Connection failure information for packet duplication

ABSTRACT

Systems, apparatuses, and methods are described for wireless communications. Devices may exchange information regarding a radio link failure and/or a handover. The information may comprise a radio link failure report which may comprise an indication of packet duplication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/918,577, filed Jul. 1, 2020, which is a continuation of U.S.application Ser. No. 16/130,696, filed Sep. 13, 2018, now U.S. Pat. No.10,757,615, which claims the benefit of U.S. Provisional Application No.62/558,116, filed on Sep. 13, 2017, the contents of which are herebyincorporated by reference in their entireties for all purposes.

BACKGROUND

In wireless communications, communication failures may occur. If acommunication failure is detected, such as a radio link failure,difficulties may arise in compensating for the communication failure.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, apparatuses, and methods are described for communicationsassociated with communication failures. Radio link failure reports maybe generated based on the communication failures and transmitted to oneor more devices. The radio link failure reports may indicate whether apacket duplication may have occurred. The one or more devices (e.g.,base stations or wireless devices) may adjust configuration parametersbased on the radio link failure reports. If a handover occurs, radiolink failure reports may be communicated between devices to promote moreeffective communication and to avoid further errors based on identifiedissues.

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows example sets of orthogonal frequency division multiplexing(OFDM) subcarriers.

FIG. 2 shows example transmission time and reception time for twocarriers in a carrier group.

FIG. 3 shows example OFDM radio resources.

FIG. 4 shows hardware elements of a base station and a wireless device.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D show examples for uplink anddownlink signal transmission.

FIG. 6 shows an example protocol structure with multi-connectivity.

FIG. 7 shows an example protocol structure with carrier aggregation (CA)and dual connectivity (DC).

FIG. 8 shows example timing advance group (TAG) configurations.

FIG. 9 shows example message flow in a random access process in asecondary TAG.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F showexamples for architectures of tight interworking between a 5G RAN and along term evolution (LTE) radio access network (RAN).

FIG. 12A, FIG. 12B, and FIG. 12C show examples for radio protocolstructures of tight interworking bearers.

FIG. 13A and FIG. 13B show examples for gNodeB (gNB) deployment.

FIG. 14 shows functional split option examples of a centralized gNBdeployment.

FIG. 15 shows an example of packet duplication and radio link failure(RLF).

FIG. 16 shows an example message flow associated with RLF.

FIG. 17 shows an example of packet duplication and RLF.

FIG. 18 shows an example message flow associated with RLF.

FIG. 19 shows an example method associated with RLF.

FIG. 20 shows an example method associated with RLF.

FIG. 21 shows an example method associated with RLF.

FIG. 22 shows an example architecture for PDCP duplication.

FIG. 23 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings, which form a part hereof, show examples ofthe disclosure. It is to be understood that the examples shown in thedrawings and/or discussed herein are non-exclusive and that there areother examples of how the disclosure may be practiced.

Examples may enable operation of carrier aggregation and may be employedin the technical field of multicarrier communication systems. Examplesmay relate to radio link failure in multicarrier communication systems.

The following acronyms are used throughout the present disclosure,provided below for convenience although other acronyms may be introducedin the detailed description:

-   -   3GPP 3rd Generation Partnership Project    -   5G 5th generation wireless systems    -   5GC 5G Core Network    -   ACK Acknowledgement    -   AMF Access and Mobility Management Function    -   ASIC application-specific integrated circuit    -   BPSK binary phase shift keying    -   CA carrier aggregation    -   CC component carrier    -   CDMA code division multiple access    -   CP cyclic prefix    -   CPLD complex programmable logic devices    -   CSI channel state information    -   CSS common search space    -   CU central unit    -   DC dual connectivity    -   DCI downlink control information    -   DFTS-OFDM discrete Fourier transform spreading OFDM    -   DL downlink    -   DU distributed unit    -   eLTE enhanced LTE    -   eMBB enhanced mobile broadband    -   eNB evolved Node B    -   EPC evolved packet core    -   E-UTRAN evolved-universal terrestrial radio access network    -   FDD frequency division multiplexing    -   FPGA field programmable gate arrays    -   Fs-C Fs-control plane    -   Fs-U Fs-user plane    -   gNB next generation node B    -   HARQ hybrid automatic repeat request    -   HDL hardware description languages    -   ID identifier    -   IE information element    -   LTE long term evolution    -   MAC media access control    -   MCG master cell group    -   MeNB master evolved node B    -   MIB master information block    -   MME mobility management entity    -   mMTC massive machine type communications    -   NACK Negative Acknowledgement    -   NAS non-access stratum    -   NG CP next generation control plane core    -   NGC next generation core    -   NG-C NG-control plane    -   NG-U NG-user plane    -   NR MAC new radio MAC    -   NR PDCP new radio PDCP    -   NR PHY new radio physical    -   NR RLC new radio RLC    -   NR RRC new radio RRC    -   NR new radio    -   NSSAI network slice selection assistance information    -   OFDM orthogonal frequency division multiplexing    -   PCC primary component carrier    -   PCell primary cell    -   PDCCH physical downlink control channel    -   PDCP packet data convergence protocol    -   PDU packet data unit    -   PHICH physical HARQ indicator channel    -   PHY physical    -   PLMN public land mobile network    -   PSCell primary secondary cell    -   pTAG primary timing advance group    -   PUCCH physical uplink control channel    -   PUSCH physical uplink shared channel    -   QAM quadrature amplitude modulation    -   QPSK quadrature phase shift keying    -   RA random access    -   RACH random access channel    -   RAN radio access network    -   RAP random access preamble    -   RAR random access response    -   RB resource blocks    -   RBG resource block groups    -   RLC radio link control    -   RRC radio resource control    -   RRM radio resource management    -   RV redundancy version    -   SCC secondary component carrier    -   SCell secondary cell    -   SCG secondary cell group    -   SC-OFDM single carrier-OFDM    -   SDU service data unit    -   SeNB secondary evolved node B    -   SFN system frame number    -   S-GW serving gateway    -   SIB system information block    -   SC-OFDM single carrier orthogonal frequency division        multiplexing    -   SRB signaling radio bearer    -   sTAG(s) secondary timing advance group(s)    -   TA timing advance    -   TAG timing advance group    -   TAI tracking area identifier    -   TAT time alignment timer    -   TDD time division duplexing    -   TDMA time division multiple access    -   TTI transmission time interval    -   TB transport block    -   UE user equipment    -   UL uplink    -   UPGW user plane gateway    -   URLLC ultra-reliable low-latency communications    -   VHDL VHSIC hardware description language    -   Xn-C Xn-control plane    -   Xn-U Xn-user plane    -   Xx-C Xx-control plane    -   Xx-U Xx-user plane

Examples may be implemented using various physical layer modulation andtransmission mechanisms. Example transmission mechanisms may include,but are not limited to: CDMA, OFDM, TDMA, Wavelet technologies, and/orthe like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may be usedfor signal transmission in the physical layer. Examples of modulationschemes include, but are not limited to: phase, amplitude, code, acombination of these, and/or the like. An example radio transmissionmethod may implement QAM using BPSK, QPSK, 16-QAM, 64-QAM, 256-QAM,and/or the like. Physical radio transmission may be enhanced bydynamically or semi-dynamically changing the modulation and codingscheme depending on transmission requirements and radio conditions.

FIG. 1 shows example sets of OFDM subcarriers. As shown in this example,arrow(s) in the diagram may depict a subcarrier in a multicarrier OFDMsystem. The OFDM system may use technology such as OFDM technology,DFTS-OFDM, SC-OFDM technology, or the like. For example, arrow 101 showsa subcarrier transmitting information symbols. FIG. 1 is shown as anexample, and a typical multicarrier OFDM system may include moresubcarriers in a carrier. For example, the number of subcarriers in acarrier may be in the range of 10 to 10,000 subcarriers. FIG. 1 showstwo guard bands 106 and 107 in a transmission band. As shown in FIG. 1 ,guard band 106 is between subcarriers 103 and subcarriers 104. Theexample set of subcarriers A 102 includes subcarriers 103 andsubcarriers 104. FIG. 1 also shows an example set of subcarriers B 105.As shown, there is no guard band between any two subcarriers in theexample set of subcarriers B 105. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 2 shows an example timing arrangement with transmission time andreception time for two carriers. A multicarrier OFDM communicationsystem may include one or more carriers, for example, ranging from 1 to10 carriers. Carrier A 204 and carrier B 205 may have the same ordifferent timing structures. Although FIG. 2 shows two synchronizedcarriers, carrier A 204 and carrier B 205 may or may not be synchronizedwith each other. Different radio frame structures may be supported forFDD and TDD duplex mechanisms. FIG. 2 shows an example FDD frame timing.Downlink and uplink transmissions may be organized into radio frames201. In this example, radio frame duration is 10 milliseconds (msec).Other frame durations, for example, in the range of 1 to 100 msec mayalso be supported. In this example, each 10 msec radio frame 201 may bedivided into ten equally sized subframes 202. Other subframe durationssuch as including 0.5 msec, 1 msec, 2 msec, and 5 msec may also besupported. Subframe(s) may consist of two or more slots (e.g., slots 206and 207). For the example of FDD, 10 subframes may be available fordownlink transmission and 10 subframes may be available for uplinktransmissions in each 10 msec interval. Uplink and downlinktransmissions may be separated in the frequency domain. A slot may be 7or 14 OFDM symbols for the same subcarrier spacing of up to 60 kHz withnormal CP. A slot may be 14 OFDM symbols for the same subcarrier spacinghigher than 60 kHz with normal CP. A slot may include all downlink, alluplink, or a downlink part and an uplink part, and/or alike. Slotaggregation may be supported, e.g., data transmission may be scheduledto span one or multiple slots. For example, a mini-slot may start at anOFDM symbol in a subframe. A mini-slot may have a duration of one ormore OFDM symbols. Slot(s) may include a plurality of OFDM symbols 203.The number of OFDM symbols 203 in a slot 206 may depend on the cyclicprefix length and subcarrier spacing.

FIG. 3 shows an example of OFDM radio resources. The resource gridstructure in time 304 and frequency 305 is shown in FIG. 3 . Thequantity of downlink subcarriers or RBs may depend, at least in part, onthe downlink transmission bandwidth 306 configured in the cell. Thesmallest radio resource unit may be called a resource element (e.g.,301). Resource elements may be grouped into resource blocks (e.g., 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g., 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other predefined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. A resource block may correspond to one slot in the timedomain and 180 kHz in the frequency domain (for 15 kHz subcarrierbandwidth and 12 subcarriers).

Multiple numerologies may be supported. A numerology may be derived byscaling a basic subcarrier spacing by an integer N. Scalable numerologymay allow at least from 15 kHz to 480 kHz subcarrier spacing. Thenumerology with 15 kHz and scaled numerology with different subcarrierspacing with the same CP overhead may align at a symbol boundary every 1msec in a NR carrier.

FIG. 4 shows hardware elements of a base station 401 and a wirelessdevice 406. A communication network 400 may include at least one basestation 401 and at least one wireless device 406. The base station 401may include at least one communication interface 402, one or moreprocessors 403, and at least one set of program code instructions 405stored in non-transitory memory 404 and executable by the one or moreprocessors 403. The wireless device 406 may include at least onecommunication interface 407, one or more processors 408, and at leastone set of program code instructions 410 stored in non-transitory memory409 and executable by the one or more processors 408. A communicationinterface 402 in the base station 401 may be configured to engage incommunication with a communication interface 407 in the wireless device406, such as via a communication path that includes at least onewireless link 411. The wireless link 411 may be a bi-directional link.The communication interface 407 in the wireless device 406 may also beconfigured to engage in communication with the communication interface402 in the base station 401. The base station 401 and the wirelessdevice 406 may be configured to send and receive data over the wirelesslink 411 using multiple frequency carriers. Base stations, wirelessdevices, and other communication devices may include structure andoperations of transceiver(s). A transceiver is a device that includesboth a transmitter and receiver. Transceivers may be employed in devicessuch as wireless devices, base stations, relay nodes, and/or the like.Examples for radio technology implemented in the communicationinterfaces 402, 407 and the wireless link 411 are shown in FIG. 1 , FIG.2 , FIG. 3 , FIG. 5 , and associated text. The communication network 400may comprise any number and/or type of devices, such as, for example,computing devices, wireless devices, mobile devices, handsets, tablets,laptops, internet of things (IoT) devices, hotspots, cellular repeaters,computing devices, and/or, more generally, user equipment (e.g., UE).Although one or more of the above types of devices may be referencedherein (e.g., UE, wireless device, computing device, etc.), it should beunderstood that any device herein may comprise any one or more of theabove types of devices or similar devices. The communication network400, and any other network referenced herein, may comprise an LTEnetwork, a 5G network, or any other network for wireless communications.Apparatuses, systems, and/or methods described herein may generally bedescribed as implemented on one or more devices (e.g., wireless device,base station, eNB, gNB, computing device, etc.), in one or morenetworks, but it will be understood that one or more features and stepsmay be implemented on any device and/or in any network. As usedthroughout, the term “base station” may comprise one or more of: a basestation, a node, a Node B, a gNB, an eNB, an ng-eNB, a relay node (e.g.,an integrated access and backhaul (IAB) node), a donor node (e.g., adonor eNB, a donor gNB, etc.), an access point (e.g., a Wi-Fi accesspoint), a computing device, a device capable of wirelesslycommunicating, or any other device capable of sending and/or receivingsignals. As used throughout, the term “wireless device” may comprise oneor more of: a UE, a handset, a mobile device, a computing device, anode, a device capable of wirelessly communicating, or any other devicecapable of sending and/or receiving signals. Any reference to one ormore of these terms/devices also considers use of any other term/devicementioned above.

The communications network 400 may comprise Radio Access Network (RAN)architecture. The RAN architecture may comprise one or more RAN nodesthat may be a next generation Node B (gNB) (e.g., 401) providing NewRadio (NR) user plane and control plane protocol terminations towards afirst wireless device (e.g. 406). A RAN node may be a next generationevolved Node B (ng-eNB), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device. The first wireless device may communicate with agNB over a Uu interface. The second wireless device may communicate witha ng-eNB over a Uu interface. Base station 401 may comprise one or moreof a gNB, ng-eNB, and/or the like.

A gNB or an ng-eNB may host functions such as: radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of wirelessdevices in RRC_INACTIVE state, distribution function for Non-AccessStratum (NAS) messages, RAN sharing, and dual connectivity or tightinterworking between NR and E-UTRA.

One or more gNBs and/or one or more ng-eNBs may be interconnected witheach other by means of Xn interface. A gNB or an ng-eNB may be connectedby means of NG interfaces to 5G Core Network (5GC). 5GC may comprise oneor more AMF/User Plane Function (UPF) functions. A gNB or an ng-eNB maybe connected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g., non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (e.g., NG-C) interface. The NG-C interface may provide functionssuch as NG interface management, UE context management, UE mobilitymanagement, transport of NAS messages, paging, PDU session management,configuration transfer or warning message transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (if applicable), external PDU sessionpoint of interconnect to data network, packet routing and forwarding,packet inspection and user plane part of policy rule enforcement,traffic usage reporting, uplink classifier to support routing trafficflows to a data network, branching point to support multi-homed PDUsession, QoS handling for user plane, e.g. packet filtering, gating,Uplink (UL)/Downlink (DL) rate enforcement, uplink traffic verification(e.g. Service Data Flow (SDF) to QoS flow mapping), downlink packetbuffering and/or downlink data notification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling for mobility between 3^(rd) GenerationPartnership Project (3GPP) access networks, idle mode UE reachability(e.g., control and execution of paging retransmission), registrationarea management, support of intra-system and inter-system mobility,access authentication, access authorization including check of roamingrights, mobility management control (subscription and policies), supportof network slicing and/or Session Management Function (SMF) selection

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or a non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ora non-operational state. In other words, the hardware, software,firmware, registers, memory values, and/or the like may be “configured”within a device, whether the device is in an operational or anonoperational state, to provide the device with specificcharacteristics. Terms such as “a control message to cause in a device”may mean that a control message has parameters that may be used toconfigure specific characteristics in the device, whether the device isin an operational or a non-operational state.

A network may include a multitude of base stations, providing a userplane NR PDCP/NR RLC/NR MAC/NR PHY and control plane (e.g., NR RRC)protocol terminations towards the wireless device. The base station(s)may be interconnected with other base station(s) (e.g., employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B show examplesfor interfaces between a 5G core network (e.g., NGC) and base stations(e.g., gNB and eLTE eNB). For example, the base stations may beinterconnected to the NGC control plane (e.g., NG CP) employing the NG-Cinterface and to the NGC user plane (e.g., UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors, for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g., TAI), and atRRC connection re-establishment/handover, one serving cell may providethe security input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC); in the uplink, thecarrier corresponding to the PCell may be the Uplink Primary ComponentCarrier (UL PCC). Depending on wireless device capabilities, SecondaryCells (SCells) may be configured to form together with the PCell a setof serving cells. In the downlink, the carrier corresponding to an SCellmay be a Downlink Secondary Component Carrier (DL SCC); in the uplink,the carrier corresponding to an SCell may be an Uplink SecondaryComponent Carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context in which it is used). The cell ID may beequally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, reference to a firstphysical cell ID for a first downlink carrier may indicate that thefirst physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.Reference to a first carrier that is activated may indicate that thecell comprising the first carrier is activated.

A device may be configured to operate as needed by freely combining anyof the examples. The disclosed mechanisms may be performed if certaincriteria are met, for example, in a wireless device, a base station, aradio environment, a network, a combination of the above, and/or thelike. Example criteria may be based, at least in part, on for example,traffic load, initial system set up, packet sizes, trafficcharacteristics, a combination of the above, and/or the like. One ormore criteria may be satisfied. It may be possible to implement examplesthat selectively implement disclosed protocols.

A base station may communicate with a variety of wireless devices.Wireless devices may support multiple technologies, and/or multiplereleases of the same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. Referenceto a base station communicating with a plurality of wireless devices mayindicate that a base station may communicate with a subset of the totalwireless devices in a coverage area. A plurality of wireless devices ofa given LTE or 5G release, with a given capability and in a given sectorof the base station, may be used. The plurality of wireless devices mayrefer to a selected plurality of wireless devices, and/or a subset oftotal wireless devices in a coverage area which perform according todisclosed methods, and/or the like. There may be a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices perform based onolder releases of LTE or 5G technology.

A base station may transmit (e.g., to a wireless device) one or moremessages (e.g. RRC messages) that may comprise a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). The other SImay be transmitted via SystemInformationBlockType2. For a wirelessdevice in an RRC_Connected state, dedicated RRC signaling may beemployed for the request and delivery of the other SI. For the wirelessdevice in the RRC_Idle state and/or the RRC_Inactive state, the requestmay trigger a random-access procedure.

A wireless device may send its radio access capability information whichmay be static. A base station may request what capabilities for awireless device to report based on band information. If allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

If CA is configured, a wireless device may have an RRC connection with anetwork. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. If adding a new SCell, dedicatedRRC signaling may be employed to send all required system information ofthe SCell. In connected mode, wireless devices may not need to acquirebroadcasted system information directly from the SCells.

An RRC connection reconfiguration procedure may be used to modify an RRCconnection, (e.g. to establish, modify and/or release RBs, to performhandover, to setup, modify, and/or release measurements, to add, modify,and/or release SCells and cell groups). As part of the RRC connectionreconfiguration procedure, NAS dedicated information may be transferredfrom the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be used to establish (or reestablish, resume) an RRC connection. AnRRC connection establishment procedure may comprise SRB1 establishment.The RRC connection establishment procedure may be used to transfer theinitial NAS dedicated information message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure, e.g., after successful securityactivation. A measurement report message may be employed to transmitmeasurement results.

FIG. 5A, FIG. 5B, FIG. 5C, and FIG. 5D show examples of architecture foruplink and downlink signal transmission. FIG. 5A shows an example for anuplink physical channel. The baseband signal representing the physicaluplink shared channel may be processed according to the followingprocesses, which may be performed by structures described below. Thesestructures and corresponding functions are shown as examples, however,it is anticipated that other structures and/or functions may beimplemented in various examples. The structures and correspondingfunctions may comprise, e.g., one or more scrambling devices 501A and501B configured to perform scrambling of coded bits in each of thecodewords to be transmitted on a physical channel; one or moremodulation mappers 502A and 502B configured to perform modulation ofscrambled bits to generate complex-valued symbols; a layer mapper 503configured to perform mapping of the complex-valued modulation symbolsonto one or several transmission layers; one or more transform precoders504A and 504B to generate complex-valued symbols; a precoding device 505configured to perform precoding of the complex-valued symbols; one ormore resource element mappers 506A and 506B configured to performmapping of precoded complex-valued symbols to resource elements; one ormore signal generators 507A and 507B configured to perform thegeneration of a complex-valued time-domain DFTS-OFDM/SC-FDMA signal foreach antenna port; and/or the like.

FIG. 5B shows an example for performing modulation and up-conversion tothe carrier frequency of the complex-valued DFTS-OFDM/SC-FDMA basebandsignal, e.g., for each antenna port and/or for the complex-valuedphysical random access channel (PRACH) baseband signal. For example, thebaseband signal, represented as s₁(t), may be split, by a signalsplitter 510, into real and imaginary components, Re{s₁(t)} andIm{s₁(t)}, respectively. The real component may be modulated by amodulator 511A, and the imaginary component may be modulated by amodulator 511B. The output signal of the modulator 511A and the outputsignal of the modulator 511B may be mixed by a mixer 512. The outputsignal of the mixer 512 may be input to a filtering device 513, andfiltering may be employed by the filtering device 513 prior totransmission.

FIG. 5C shows an example structure for downlink transmissions. Thebaseband signal representing a downlink physical channel may beprocessed by the following processes, which may be performed bystructures described below. These structures and corresponding functionsare shown as examples, however, it is anticipated that other structuresand/or functions may be implemented in various examples. The structuresand corresponding functions may comprise, e.g., one or more scramblingdevices 531A and 531B configured to perform scrambling of coded bits ineach of the codewords to be transmitted on a physical channel; one ormore modulation mappers 532A and 532B configured to perform modulationof scrambled bits to generate complex-valued modulation symbols; a layermapper 533 configured to perform mapping of the complex-valuedmodulation symbols onto one or several transmission layers; a precodingdevice 535 configured to perform precoding of the complex-valuedmodulation symbols on each layer for transmission on the antenna ports;one or more resource element mappers 536A and 536B configured to performmapping of complex-valued modulation symbols for each antenna port toresource elements; one or more OFDM signal generators 537A and 537Bconfigured to perform the generation of complex-valued time-domain OFDMsignal for each antenna port; and/or the like.

FIG. 5D shows an example structure for modulation and up-conversion tothe carrier frequency of the complex-valued OFDM baseband signal foreach antenna port. For example, the baseband signal, represented as s₁^((p))(t), may be split, by a signal splitter 520, into real andimaginary components, Re{s₁ ^((p))(t)} and Im{s₁ ^((p))(t)},respectively. The real component may be modulated by a modulator 521A,and the imaginary component may be modulated by a modulator 521B. Theoutput signal of the modulator 521A and the output signal of themodulator 521B may be mixed by a mixer 522. The output signal of themixer 522 may be input to a filtering device 523, and filtering may beemployed by the filtering device 523 prior to transmission.

FIG. 6 and FIG. 7 show examples for protocol structures with CA andmulti-connectivity. NR may support multi-connectivity operation, wherebya multiple receiver/transmitter (RX/TX) wireless device in RRC_CONNECTEDmay be configured to utilize radio resources provided by multipleschedulers located in multiple gNBs connected via a non-ideal or idealbackhaul over the Xn interface. gNBs involved in multi-connectivity fora certain wireless device may assume two different roles: a gNB mayeither act as a master gNB (e.g., 600) or as a secondary gNB (e.g., 610or 620). In multi-connectivity, a wireless device may be connected toone master gNB (e.g., 600) and one or more secondary gNBs (e.g., 610and/or 620). Any one or more of the Master gNB 600 and/or the secondarygNBs 610 and 620 may be a Next Generation (NG) NodeB. The master gNB 600may comprise protocol layers NR MAC 601, NR RLC 602 and 603, and NR PDCP604 and 605. The secondary gNB may comprise protocol layers NR MAC 611,NR RLC 612 and 613, and NR PDCP 614. The secondary gNB may compriseprotocol layers NR MAC 620, NR RLC 622 and 623, and NR PDCP 624. Themaster gNB 600 may communicate via an interface 606 and/or via aninterface 607, the secondary gNB 610 may communicate via an interface615, and the secondary gNB 620 may communicate via an interface 625. Themaster gNB 600 may also communicate with the secondary gNB 610 and thesecondary gNB 621 via interfaces 608 and 609, respectively, which mayinclude Xn interfaces. For example, the master gNB 600 may communicatevia the interface 608, at layer NR PDCP 605, and with the secondary gNB610 at layer NR RLC 612. The master gNB 600 may communicate via theinterface 609, at layer NR PDCP 605, and with the secondary gNB 620 atlayer NR RLC 622.

FIG. 7 shows an example structure for the UE side MAC entities, e.g., ifa Master Cell Group (MCG) and a Secondary Cell Group (SCG) areconfigured. Media Broadcast Multicast Service (MBMS) reception may beincluded but is not shown in this figure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is set up. As an example, threealternatives may exist, an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 6 . NR RRC may be located in a master gNBand SRBs may be configured as a MCG bearer type and may use the radioresources of the master gNB. Multi-connectivity may have at least onebearer configured to use radio resources provided by the secondary gNB.Multi-connectivity may or may not be configured or implemented.

For multi-connectivity, the wireless device may be configured withmultiple NR MAC entities: e.g., one NR MAC entity for a master gNB, andother NR MAC entities for secondary gNBs. In multi-connectivity, theconfigured set of serving cells for a wireless device may comprise twosubsets: e.g., the Master Cell Group (MCG) including the serving cellsof the master gNB, and the Secondary Cell Groups (SCGs) including theserving cells of the secondary gNBs.

At least one cell in a SCG may have a configured UL component carrier(CC) and one of the UL CCs, e.g., named PSCell (or PCell of SCG, orsometimes called PCell), may be configured with PUCCH resources. If theSCG is configured, there may be at least one SCG bearer or one splitbearer. If a physical layer problem or a random access problem on aPSCell occurs or is detected, if the maximum number of NR RLCretransmissions has been reached associated with the SCG, or if anaccess problem on a PSCell during a SCG addition or a SCG change occursor is detected, then an RRC connection re-establishment procedure maynot be triggered, UL transmissions towards cells of the SCG may bestopped, a master gNB may be informed by the wireless device of a SCGfailure type, and for a split bearer the DL data transfer over themaster gNB may be maintained. The NR RLC Acknowledge Mode (AM) bearermay be configured for the split bearer Like the PCell, a PSCell may notbe de-activated. The PSCell may be changed with an SCG change (e.g.,with a security key change and a RACH procedure). A direct bearer typemay change between a split bearer and an SCG bearer, or a simultaneousconfiguration of an SCG and a split bearer may or may not be supported.

A master gNB and secondary gNBs may interact for multi-connectivity. Themaster gNB may maintain the RRM measurement configuration of thewireless device, and the master gNB may, (e.g., based on receivedmeasurement reports, and/or based on traffic conditions and/or bearertypes), decide to ask a secondary gNB to provide additional resources(e.g., serving cells) for a wireless device. If a request from themaster gNB is received, a secondary gNB may create a container that mayresult in the configuration of additional serving cells for the wirelessdevice (or the secondary gNB decide that it has no resource available todo so). For wireless device capability coordination, the master gNB mayprovide some or all of the Active Set (AS) configuration and thewireless device capabilities to the secondary gNB. The master gNB andthe secondary gNB may exchange information about a wireless deviceconfiguration, such as by employing NR RRC containers (e.g., inter-nodemessages) carried in Xn messages. The secondary gNB may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary gNB). The secondary gNB may decide which cell is the PSCellwithin the SCG. The master gNB may or may not change the content of theNR RRC configuration provided by the secondary gNB. In an SCG additionand an SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s). Both a master gNB and asecondary gNBs may know the system frame number (SFN) and subframeoffset of each other by operations, administration, and maintenance(OAM) (e.g., for the purpose of discontinuous reception (DRX) alignmentand identification of a measurement gap). If adding a new SCG SCell,dedicated NR RRC signaling may be used for sending required systeminformation of the cell for CA, except, e.g., for the SFN acquired froman MIB of the PSCell of an SCG.

FIG. 7 shows an example of dual-connectivity (DC) for two MAC entitiesat a wireless device side. A first MAC entity may comprise a lower layerof an MCG 700, an upper layer of an MCG 718, and one or moreintermediate layers of an MCG 719. The lower layer of the MCG 700 maycomprise, e.g., a paging channel (PCH) 701, a broadcast channel (BCH)702, a downlink shared channel (DL-SCH) 703, an uplink shared channel(UL-SCH) 704, and a random access channel (RACH) 705. The one or moreintermediate layers of the MCG 719 may comprise, e.g., one or morehybrid automatic repeat request (HARM) processes 706, one or more randomaccess control processes 707, multiplexing and/or de-multiplexingprocesses 709, logical channel prioritization on the uplink processes710, and a control processes 708 providing control for the aboveprocesses in the one or more intermediate layers of the MCG 719. Theupper layer of the MCG 718 may comprise, e.g., a paging control channel(PCCH) 711, a broadcast control channel (BCCH) 712, a common controlchannel (CCCH) 713, a dedicated control channel (DCCH) 714, a dedicatedtraffic channel (DTCH) 715, and a MAC control 716.

A second MAC entity may comprise a lower layer of an SCG 720, an upperlayer of an SCG 738, and one or more intermediate layers of an SCG 739.The lower layer of the SCG 720 may comprise, e.g., a BCH 722, a DL-SCH723, an UL-SCH 724, and a RACH 725. The one or more intermediate layersof the SCG 739 may comprise, e.g., one or more HARQ processes 726, oneor more random access control processes 727, multiplexing and/orde-multiplexing processes 729, logical channel prioritization on theuplink processes 730, and a control processes 728 providing control forthe above processes in the one or more intermediate layers of the SCG739. The upper layer of the SCG 738 may comprise, e.g., a BCCH 732, aDCCH 714, a DTCH 735, and a MAC control 736.

Serving cells may be grouped in a TA group (TAG). Serving cells in oneTAG may use the same timing reference. For a given TAG, a wirelessdevice may use at least one downlink carrier as a timing reference. Fora given TAG, a wireless device may synchronize uplink subframe and frametransmission timing of uplink carriers belonging to the same TAG.Serving cells having an uplink to which the same TA applies maycorrespond to serving cells hosted by the same receiver. A wirelessdevice supporting multiple TAs may support two or more TA groups. One TAgroup may include the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not include thePCell and may be called a secondary TAG (sTAG). Carriers within the sameTA group may use the same TA value and/or the same timing reference. IfDC is configured, cells belonging to a cell group (e.g., MCG or SCG) maybe grouped into multiple TAGs including a pTAG and one or more sTAGs.

FIG. 8 shows example TAG configurations. In Example 1, a pTAG comprisesa PCell, and an sTAG comprises an SCell1. In Example 2, a pTAG comprisesa PCell and an SCell1, and an sTAG comprises an SCell2 and an SCell3. InExample 3, a pTAG comprises a PCell and an SCell1, and an sTAG1comprises an SCell2 and an SCell3, and an sTAG2 comprises a SCell4. Upto four TAGs may be supported in a cell group (MCG or SCG), and otherexample TAG configurations may also be provided. In various examples,structures and operations are described for use with a pTAG and an sTAG.Some of the examples may be used for configurations with multiple sTAGs.

An eNB may initiate an RA procedure, via a PDCCH order, for an activatedSCell. The PDCCH order may be sent on a scheduling cell of this SCell.If cross carrier scheduling is configured for a cell, the schedulingcell may be different than the cell that is employed for preambletransmission, and the PDCCH order may include an SCell index. At least anon-contention based RA procedure may be supported for SCell(s) assignedto sTAG(s).

FIG. 9 shows an example of random access processes, and a correspondingmessage flow, in a secondary TAG. A base station, such as an eNB, maytransmit an activation command 900 to a wireless device, such as a UE.The activation command 900 may be transmitted to activate an SCell. Thebase station may also transmit a PDCCH order 901 to the wireless device,which may be transmitted, e.g., after the activation command 900. Thewireless device may begin to perform a RACH process for the SCell, whichmay be initiated, e.g., after receiving the PDCCH order 901. A wirelessdevice may transmit to the base station (e.g., as part of a RACHprocess) a preamble 902 (e.g., Msg1), such as a random access preamble(RAP). The preamble 902 may be transmitted in response to the PDCCHorder 901. The wireless device may transmit the preamble 902 via anSCell belonging to an sTAG. Preamble transmission for SCells may becontrolled by a network using PDCCH format 1A. The base station may senda random access response (RAR) 903 (e.g., Msg2 message) to the wirelessdevice. The RAR 903 may be in response to the preamble 902 transmissionvia the SCell. The RAR 903 may be addressed to a random access radionetwork temporary identifier (RA-RNTI) in a PCell common search space(CSS). If the wireless device receives the RAR 903, the RACH process mayconclude. The RACH process may conclude, e.g., after or in response tothe wireless device receiving the RAR 903 from the base station. Afterthe RACH process, the wireless device may transmit an uplinktransmission 904. The uplink transmission 904 may comprise uplinkpackets transmitted via the same SCell used for the preamble 902transmission.

Initial timing alignment for communications between the wireless deviceand the base station may be performed through a random access procedure,such as described above regarding FIG. 9 . The random access proceduremay involve a wireless device, such as a UE, transmitting a randomaccess preamble and a base station, such as an eNB, responding with aninitial TA command NTA (amount of timing advance) within a random accessresponse window. The start of the random access preamble may be alignedwith the start of a corresponding uplink subframe at the wireless deviceassuming NTA=0. The eNB may estimate the uplink timing from the randomaccess preamble transmitted by the wireless device. The TA command maybe derived by the eNB based on the estimation of the difference betweenthe desired UL timing and the actual UL timing. The wireless device maydetermine the initial uplink transmission timing relative to thecorresponding downlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. If an eNB performs anSCell addition configuration, the related TAG configuration may beconfigured for the SCell. An eNB may modify the TAG configuration of anSCell by removing (e.g., releasing) the SCell and adding (e.g.,configuring) a new SCell (with the same physical cell ID and frequency)with an updated TAG ID. The new SCell with the updated TAG ID mayinitially be inactive subsequent to being assigned the updated TAG ID.The eNB may activate the updated new SCell and start scheduling packetson the activated SCell. In some examples, it may not be possible tochange the TAG associated with an SCell, but rather, the SCell may needto be removed and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, such as at least one RRC reconfiguration message,may be sent to the wireless device. The at least one RRC message may besent to the wireless device to reconfigure TAG configurations, e.g., byreleasing the SCell and configuring the SCell as a part of the pTAG. If,e.g., an SCell is added or configured without a TAG index, the SCell maybe explicitly assigned to the pTAG. The PCell may not change its TAgroup and may be a member of the pTAG.

In LTE Release-10 and Release-11 CA, a PUCCH transmission is onlytransmitted on a PCell (e.g., a PSCell) to an eNB. In LTE-Release 12 andearlier, a wireless device may transmit PUCCH information on one cell(e.g., a PCell or a PSCell) to a given eNB. As the number of CA capablewireless devices increase, and as the number of aggregated carriersincrease, the number of PUCCHs and the PUCCH payload size may increase.Accommodating the PUCCH transmissions on the PCell may lead to a highPUCCH load on the PCell. A PUCCH on an SCell may be used to offload thePUCCH resource from the PCell. More than one PUCCH may be configured.For example, a PUCCH on a PCell may be configured and another PUCCH onan SCell may be configured. One, two, or more cells may be configuredwith PUCCH resources for transmitting CSI, acknowledgment (ACK), and/ornon-acknowledgment (NACK) to a base station. Cells may be grouped intomultiple PUCCH groups, and one or more cell within a group may beconfigured with a PUCCH. In some examples, one SCell may belong to onePUCCH group. SCells with a configured PUCCH transmitted to a basestation may be called a PUCCH SCell, and a cell group with a commonPUCCH resource transmitted to the same base station may be called aPUCCH group.

A MAC entity may have a configurable timer, e.g., timeAlignmentTimer,per TAG. The timeAlignmentTimer may be used to control how long the MACentity considers the serving cells belonging to the associated TAG to beuplink time aligned. If a Timing Advance Command MAC control element isreceived, the MAC entity may apply the Timing Advance Command for theindicated TAG; and/or the MAC entity may start or restart thetimeAlignmentTimer associated with a TAG that may be indicated by theTiming Advance Command MAC control element. If a Timing Advance Commandis received in a Random Access Response message for a serving cellbelonging to a TAG, the MAC entity may apply the Timing Advance Commandfor this TAG and/or start or restart the timeAlignmentTimer associatedwith this TAG. Additionally or alternatively, if the Random AccessPreamble is not selected by the MAC entity, the MAC entity may apply theTiming Advance Command for this TAG and/or start or restart thetimeAlignmentTimer associated with this TAG. If the timeAlignmentTimerassociated with this TAG is not running, the Timing Advance Command forthis TAG may be applied, and the timeAlignmentTimer associated with thisTAG may be started. If the contention resolution is not successful, atimeAlignmentTimer associated with this TAG may be stopped. If thecontention resolution is successful, the MAC entity may ignore thereceived Timing Advance Command. The MAC entity may determine whetherthe contention resolution is successful or whether the contentionresolution is not successful.

FIG. 10A and FIG. 10B show examples for interfaces between a 5G corenetwork (e.g., NGC) and base stations (e.g., gNB and eLTE eNB). A basestation, such as a gNB 1020, may be interconnected to an NGC 1010control plane employing an NG-C interface. The base station, e.g., thegNB 1020, may also be interconnected to an NGC 1010 user plane (e.g.,UPGW) employing an NG-U interface. As another example, a base station,such as an eLTE eNB 1040, may be interconnected to an NGC 1030 controlplane employing an NG-C interface. The base station, e.g., the eLTE eNB1040, may also be interconnected to an NGC 1030 user plane (e.g., UPGW)employing an NG-U interface. An NG interface may support a many-to-manyrelation between 5G core networks and base stations.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexamples for architectures of tight interworking between a 5G RAN and anLTE RAN. The tight interworking may enable a multiplereceiver/transmitter (RX/TX) wireless device in an RRC_CONNECTED stateto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g., an eLTE eNB and a gNB). The two basestations may be connected via a non-ideal or ideal backhaul over the Xxinterface between an LTE eNB and a gNB, or over the Xn interface betweenan eLTE eNB and a gNB. Base stations involved in tight interworking fora certain wireless device may assume different roles. For example, abase station may act as a master base station or a base station may actas a secondary base station. In tight interworking, a wireless devicemay be connected to both a master base station and a secondary basestation. Mechanisms implemented in tight interworking may be extended tocover more than two base stations.

A master base station may be an LTE eNB 1102A or an LTE eNB 1102B, whichmay be connected to EPC nodes 1101A or 1101B, respectively. Thisconnection to EPC nodes may be, e.g., to an MME via the S1-C interfaceand/or to an S-GW via the S1-U interface. A secondary base station maybe a gNB 1103A or a gNB 1103B, either or both of which may be anon-standalone node having a control plane connection via an Xx-Cinterface to an LTE eNB (e.g., the LTE eNB 1102A or the LTE eNB 1102B).In the tight interworking architecture of FIG. 11A, a user plane for agNB (e.g., the gNB 1103A) may be connected to an S-GW (e.g., the EPC1101A) through an LTE eNB (e.g., the LTE eNB 1102A), via an Xx-Uinterface between the LTE eNB and the gNB, and via an S1-U interfacebetween the LTE eNB and the S-GW. In the architecture of FIG. 11B, auser plane for a gNB (e.g., the gNB 1103B) may be connected directly toan S-GW (e.g., the EPC 1101B) via an S1-U interface between the gNB andthe S-GW.

A master base station may be a gNB 1103C or a gNB 1103D, which may beconnected to NGC nodes 1101C or 1101D, respectively. This connection toNGC nodes may be, e.g., to a control plane core node via the NG-Cinterface and/or to a user plane core node via the NG-U interface. Asecondary base station may be an eLTE eNB 1102C or an eLTE eNB 1102D,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to a gNB (e.g., the gNB 1103C orthe gNB 1103D). In the tight interworking architecture of FIG. 11C, auser plane for an eLTE eNB (e.g., the eLTE eNB 1102C) may be connectedto a user plane core node (e.g., the NGC 1101C) through a gNB (e.g., thegNB 1103C), via an Xn-U interface between the eLTE eNB and the gNB, andvia an NG-U interface between the gNB and the user plane core node. Inthe architecture of FIG. 11D, a user plane for an eLTE eNB (e.g., theeLTE eNB 1102D) may be connected directly to a user plane core node(e.g., the NGC 1101D) via an NG-U interface between the eLTE eNB and theuser plane core node.

A master base station may be an eLTE eNB 1102E or an eLTE eNB 1102F,which may be connected to NGC nodes 1101E or 1101F, respectively. Thisconnection to NGC nodes may be, e.g., to a control plane core node viathe NG-C interface and/or to a user plane core node via the NG-Uinterface. A secondary base station may be a gNB 1103E or a gNB 1103F,either or both of which may be a non-standalone node having a controlplane connection via an Xn-C interface to an eLTE eNB (e.g., the eLTEeNB 1102E or the eLTE eNB 1102F). In the tight interworking architectureof FIG. 11E, a user plane for a gNB (e.g., the gNB 1103E) may beconnected to a user plane core node (e.g., the NGC 1101E) through aneLTE eNB (e.g., the eLTE eNB 1102E), via an Xn-U interface between theeLTE eNB and the gNB, and via an NG-U interface between the eLTE eNB andthe user plane core node. In the architecture of FIG. 11F, a user planefor a gNB (e.g., the gNB 1103F) may be connected directly to a userplane core node (e.g., the NGC 1101F) via an NG-U interface between thegNB and the user plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are examples for radio protocolstructures of tight interworking bearers.

An LTE eNB 1201A may be an S1 master base station, and a gNB 1210A maybe an S1 secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The LTE eNB1201A may be connected to an EPC with a non-standalone gNB 1210A, via anXx interface between the PDCP 1206A and an NR RLC 1212A. The LTE eNB1201A may include protocol layers MAC 1202A, RLC 1203A and RLC 1204A,and PDCP 1205A and PDCP 1206A. An MCG bearer type may interface with thePDCP 1205A, and a split bearer type may interface with the PDCP 1206A.The gNB 1210A may include protocol layers NR MAC 1211A, NR RLC 1212A andNR RLC 1213A, and NR PDCP 1214A. An SCG bearer type may interface withthe NR PDCP 1214A.

A gNB 1201B may be an NG master base station, and an eLTE eNB 1210B maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The gNB1201B may be connected to an NGC with a non-standalone eLTE eNB 1210B,via an Xn interface between the NR PDCP 1206B and an RLC 1212B. The gNB1201B may include protocol layers NR MAC 1202B, NR RLC 1203B and NR RLC1204B, and NR PDCP 1205B and NR PDCP 1206B. An MCG bearer type mayinterface with the NR PDCP 1205B, and a split bearer type may interfacewith the NR PDCP 1206B. The eLTE eNB 1210B may include protocol layersMAC 1211B, RLC 1212B and RLC 1213B, and PDCP 1214B. An SCG bearer typemay interface with the PDCP 1214B.

An eLTE eNB 1201C may be an NG master base station, and a gNB 1210C maybe an NG secondary base station. An example for a radio protocolarchitecture for a split bearer and an SCG bearer is shown. The eLTE eNB1201C may be connected to an NGC with a non-standalone gNB 1210C, via anXn interface between the PDCP 1206C and an NR RLC 1212C. The eLTE eNB1201C may include protocol layers MAC 1202C, RLC 1203C and RLC 1204C,and PDCP 1205C and PDCP 1206C. An MCG bearer type may interface with thePDCP 1205C, and a split bearer type may interface with the PDCP 1206C.The gNB 1210C may include protocol layers NR MAC 1211C, NR RLC 1212C andNR RLC 1213C, and NR PDCP 1214C. An SCG bearer type may interface withthe NR PDCP 1214C.

In a 5G network, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. At least threealternatives may exist, e.g., an MCG bearer, an SCG bearer, and a splitbearer, such as shown in FIG. 12A, FIG. 12B, and FIG. 12C. The NR RRCmay be located in a master base station, and the SRBs may be configuredas an MCG bearer type and may use the radio resources of the master basestation. Tight interworking may have at least one bearer configured touse radio resources provided by the secondary base station. Tightinterworking may or may not be configured or implemented.

The wireless device may be configured with two MAC entities: e.g., oneMAC entity for a master base station, and one MAC entity for a secondarybase station. In tight interworking, the configured set of serving cellsfor a wireless device may comprise of two subsets: e.g., the Master CellGroup (MCG) including the serving cells of the master base station, andthe Secondary Cell Group (SCG) including the serving cells of thesecondary base station.

At least one cell in a SCG may have a configured UL CC and one of them,e.g., a PSCell (or the PCell of the SCG, which may also be called aPCell), is configured with PUCCH resources. If the SCG is configured,there may be at least one SCG bearer or one split bearer. If one or moreof a physical layer problem or a random access problem is detected on aPSCell, if the maximum number of (NR) RLC retransmissions associatedwith the SCG has been reached, and/or if an access problem on a PSCellduring an SCG addition or during an SCG change is detected, then: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of the SCG may be stopped, a master basestation may be informed by the wireless device of a SCG failure type,and/or for a split bearer the DL data transfer over the master basestation may be maintained. The RLC AM bearer may be configured for thesplit bearer. Like the PCell, a PSCell may not be de-activated. A PSCellmay be changed with an SCG change, e.g., with security key change and aRACH procedure. A direct bearer type change, between a split bearer andan SCG bearer, may not be supported. Simultaneous configuration of anSCG and a split bearer may not be supported.

A master base station and a secondary base station may interact. Themaster base station may maintain the RRM measurement configuration ofthe wireless device. The master base station may determine to ask asecondary base station to provide additional resources (e.g., servingcells) for a wireless device. This determination may be based on, e.g.,received measurement reports, traffic conditions, and/or bearer types.If a request from the master base station is received, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the wireless device, or the secondary basestation may determine that it has no resource available to do so. Themaster base station may provide at least part of the AS configurationand the wireless device capabilities to the secondary base station,e.g., for wireless device capability coordination. The master basestation and the secondary base station may exchange information about awireless device configuration such as by using RRC containers (e.g.,inter-node messages) carried in Xn or Xx messages. The secondary basestation may initiate a reconfiguration of its existing serving cells(e.g., PUCCH towards the secondary base station). The secondary basestation may determine which cell is the PSCell within the SCG. Themaster base station may not change the content of the RRC configurationprovided by the secondary base station. If an SCG is added and/or an SCGSCell is added, the master base station may provide the latestmeasurement results for the SCG cell(s). Either or both of a master basestation and a secondary base station may know the SFN and subframeoffset of each other by OAM, (e.g., for the purpose of DRX alignment andidentification of a measurement gap). If a new SCG SCell is added,dedicated RRC signaling may be used for sending required systeminformation of the cell, such as for CA, except, e.g., for the SFNacquired from an MIB of the PSCell of an SCG.

FIG. 13A and FIG. 13B show examples for gNB deployment. A core 1301 anda core 1310 may interface with other nodes via RAN-CN interfaces. In anon-centralized deployment example, the full protocol stack (e.g., NRRRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported at one node,such as a gNB 1302, a gNB 1303, and/or an eLTE eNB or LTE eNB 1304.These nodes (e.g., the gNB 1302, the gNB 1303, and the eLTE eNB or LTEeNB 1304) may interface with one of more of each other via a respectiveinter-BS interface. In a centralized deployment example, upper layers ofa gNB may be located in a Central Unit (CU) 1311, and lower layers ofthe gNB may be located in Distributed Units (DU) 1312, 1313, and 1314.The CU-DU interface (e.g., Fs interface) connecting CU 1311 and DUs1312, 1312, and 1314 may be ideal or non-ideal. The Fs-C may provide acontrol plane connection over the Fs interface, and the Fs-U may providea user plane connection over the Fs interface. In the centralizeddeployment, different functional split options between the CU 1311 andthe DUs 1312, 1313, and 1314 may be possible by locating differentprotocol layers (e.g., RAN functions) in the CU 1311 and in the DU 1312,1313, and 1314. The functional split may support flexibility to move theRAN functions between the CU 1311 and the DUs 1312, 1313, and 1314depending on service requirements and/or network environments. Thefunctional split option may change during operation (e.g., after the Fsinterface setup procedure), or the functional split option may changeonly in the Fs setup procedure (e.g., the functional split option may bestatic during operation after Fs setup procedure).

FIG. 14 shows examples for different functional split options of acentralized gNB deployment. Element numerals that are followed by “A” or“B” designations in FIG. 14 may represent the same elements in differenttraffic flows, e.g., either receiving data (e.g., data 1402A) or sendingdata (e.g., 1402B). In the split option example 1, an NR RRC 1401 may bein a CU, and an NR PDCP 1403, an NR RLC (e.g., comprising a High NR RLC1404 and/or a Low NR RLC 1405), an NR MAC (e.g., comprising a High NRMAC 1406 and/or a Low NR MAC 1407), an NR PHY (e.g., comprising a HighNR PHY 1408 and/or a LOW NR PHY 1409), and an RF 1410 may be in a DU. Inthe split option example 2, the NR RRC 1401 and the NR PDCP 1403 may bein a CU, and the NR RLC, the NR MAC, the NR PHY, and the RF 1410 may bein a DU. In the split option example 3, the NR RRC 1401, the NR PDCP1403, and a partial function of the NR RLC (e.g., the High NR RLC 1404)may be in a CU, and the other partial function of the NR RLC (e.g., theLow NR RLC 1405), the NR MAC, the NR PHY, and the RF 1410 may be in aDU. In the split option example 4, the NR RRC 1401, the NR PDCP 1403,and the NR RLC may be in a CU, and the NR MAC, the NR PHY, and the RF1410 may be in a DU. In the split option example 5, the NR RRC 1401, theNR PDCP 1403, the NR RLC, and a partial function of the NR MAC (e.g.,the High NR MAC 1406) may be in a CU, and the other partial function ofthe NR MAC (e.g., the Low NR MAC 1407), the NR PHY, and the RF 1410 maybe in a DU. In the split option example 6, the NR RRC 1401, the NR PDCP1403, the NR RLC, and the NR MAC may be in CU, and the NR PHY and the RF1410 may be in a DU. In the split option example 7, the NR RRC 1401, theNR PDCP 1403, the NR RLC, the NR MAC, and a partial function of the NRPHY (e.g., the High NR PHY 1408) may be in a CU, and the other partialfunction of the NR PHY (e.g., the Low NR PHY 1409) and the RF 1410 maybe in a DU. In the split option example 8, the NR RRC 1401, the NR PDCP1403, the NR RLC, the NR MAC, and the NR PHY may be in a CU, and the RF1410 may be in a DU.

The functional split may be configured per CU, per DU, per wirelessdevice, per bearer, per slice, and/or with other granularities. In a perCU split, a CU may have a fixed split, and DUs may be configured tomatch the split option of the CU. In a per DU split, each DU may beconfigured with a different split, and a CU may provide different splitoptions for different DUs. In a per wireless device split, a gNB (e.g.,a CU and a DU) may provide different split options for differentwireless devices. In a per bearer split, different split options may beutilized for different bearer types. In a per slice splice, differentsplit options may be applied for different slices.

A new radio access network (new RAN) may support different networkslices, which may allow differentiated treatment customized to supportdifferent service requirements with end to end scope. The new RAN mayprovide a differentiated handling of traffic for different networkslices that may be pre-configured, and the new RAN may allow a singleRAN node to support multiple slices. The new RAN may support selectionof a RAN part for a given network slice, e.g., by one or more sliceID(s) or NSSAI(s) provided by a wireless device or provided by an NGC(e.g., an NG CP). The slice ID(s) or NSSAI(s) may identify one or moreof pre-configured network slices in a PLMN. For an initial attach, awireless device may provide a slice ID and/or an NSSAI, and a RAN node(e.g., a gNB) may use the slice ID or the NSSAI for routing an initialNAS signaling to an NGC control plane function (e.g., an NG CP). If awireless device does not provide any slice ID or NSSAI, a RAN node maysend a NAS signaling to a default NGC control plane function. Forsubsequent accesses, the wireless device may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. If the RAN resource isolation is implemented, shortageof shared resources in one slice does not cause a break in a servicelevel agreement for another slice.

The amount of data traffic carried over networks is expected to increasefor many years to come. The number of users and/or devices is increasingand each user/device accesses an increasing number and variety ofservices, e.g., video delivery, large files, and images. This requiresnot only high capacity in the network, but also provisioning very highdata rates to meet customers' expectations on interactivity andresponsiveness. More spectrum may be required for network operators tomeet the increasing demand. Considering user expectations of high datarates along with seamless mobility, it is beneficial that more spectrumbe made available for deploying macro cells as well as small cells forcommunication systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, if present, may be an effectivecomplement to licensed spectrum for network operators, e.g., to helpaddress the traffic explosion in some examples, such as hotspot areas.Licensed Assisted Access (LAA) offers an alternative for operators tomake use of unlicensed spectrum, e.g., if managing one radio network,offering new possibilities for optimizing the network's efficiency.

Listen-before-talk (clear channel assessment) may be implemented fortransmission in an LAA cell. In a listen-before-talk (LBT) procedure,equipment may apply a clear channel assessment (CCA) check before usingthe channel. For example, the CCA may utilize at least energy detectionto determine the presence or absence of other signals on a channel todetermine if a channel is occupied or clear, respectively. For example,European and Japanese regulations mandate the usage of LBT in theunlicensed bands. Apart from regulatory requirements, carrier sensingvia LBT may be one way for fair sharing of the unlicensed spectrum.

Discontinuous transmission on an unlicensed carrier with limited maximumtransmission duration may be enabled. Some of these functions may besupported by one or more signals to be transmitted from the beginning ofa discontinuous LAA downlink transmission. Channel reservation may beenabled by the transmission of signals, by an LAA node, after gainingchannel access, e.g., via a successful LBT operation, so that othernodes that receive the transmitted signal with energy above a certainthreshold sense the channel to be occupied. Functions that may need tobe supported by one or more signals for LAA operation with discontinuousdownlink transmission may include one or more of the following:detection of the LAA downlink transmission (including cellidentification) by wireless devices, time synchronization of wirelessdevices, and frequency synchronization of wireless devices.

DL LAA design may employ subframe boundary alignment according to LTE-Acarrier aggregation timing relationships across serving cells aggregatedby CA. This may not indicate that the eNB transmissions may start onlyat the subframe boundary. LAA may support transmitting PDSCH if not allOFDM symbols are available for transmission in a subframe according toLBT. Delivery of necessary control information for the PDSCH may also besupported.

LBT procedures may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum may require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. Nodes may follow such regulatory requirements. Anode may optionally use a lower threshold for energy detection than thatspecified by regulatory requirements. LAA may employ a mechanism toadaptively change the energy detection threshold, e.g., LAA may employ amechanism to adaptively lower the energy detection threshold from anupper bound. Adaptation mechanism may not preclude static or semi-staticsetting of the threshold. A Category 4 LBT mechanism or other type ofLBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. For some signals, insome implementation scenarios, in some situations, and/or in somefrequencies, no LBT procedure may performed by the transmitting entity.For example, Category 2 (e.g., LBT without random back-off) may beimplemented. The duration of time that the channel is sensed to be idlebefore the transmitting entity transmits may be deterministic. Forexample, Category 3 (e.g., LBT with random back-off with a contentionwindow of fixed size) may be implemented. The LBT procedure may have thefollowing procedure as one of its components. The transmitting entitymay draw a random number N within a contention window. The size of thecontention window may be specified by the minimum and maximum value ofN. The size of the contention window may be fixed. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle, e.g., before the transmittingentity transmits on the channel. For example, Category 4 (e.g., LBT withrandom back-off with a contention window of variable size) may beimplemented. The transmitting entity may draw a random number N within acontention window. The size of contention window may be specified by theminimum and maximum value of N. The transmitting entity may vary thesize of the contention window if drawing the random number N. The randomnumber N may be used in the LBT procedure to determine the duration oftime that the channel is sensed to be idle, e.g., before thetransmitting entity transmits on the channel.

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme, e.g., by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

LAA may use uplink LBT at the wireless device. The UL LBT scheme may bedifferent from the DL LBT scheme, e.g., by using different LBTmechanisms or parameters. These differences in schemes may be due to theLAA UL being based on scheduled access, which may affect a wirelessdevice's channel contention opportunities. Other considerationsmotivating a different UL LBT scheme may include, but are not limitedto, multiplexing of multiple wireless devices in a single subframe.

A DL transmission burst may be a continuous transmission from a DLtransmitting node, e.g., with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from awireless device perspective may be a continuous transmission from awireless device, e.g., with no transmission immediately before or afterfrom the same wireless device on the same CC. A UL transmission burstmay be defined from a wireless device perspective or from an eNBperspective. If an eNB is operating DL and UL LAA over the sameunlicensed carrier, DL transmission burst(s) and UL transmissionburst(s) on LAA may be scheduled in a TDM manner over the sameunlicensed carrier. An instant in time may be part of a DL transmissionburst or part of an UL transmission burst.

Packet data convergence protocol (PDCP) packet duplication may be usedto increase radio link reliability for a wireless device. For example,if a packet from a wireless device is not received by a target device(e.g., a base station), a duplicated packet may be received by thetarget device which may increase reliability of communications betweenthe wireless device and the target device. If a connection failureoccurs and PDCP packet duplication is activated, a radio link quality ofthe wireless device may be worse than when a connection failure occurswithout PDCP duplication activated. The wireless device may send, to abase station, a connection failure that may indicate whether PDCP packetduplication was activated or deactivated in relation to, or at a timeassociated with, the connection failure. The base station may determinea configuration, and/or a reconfiguration, of one or more radioresources based on whether PDCP packet duplication was activated ordeactivated in relation to, or at a time associated with, the connectionfailure. By considering whether PDCP packet duplication was activated ordeactivated, the base station may be able to more efficiently configureand/or reconfigure the one or more radio resources. For example, if aconnection failure occurs without PDCP duplication, radio conditions maybe poorer than if a connection failure occurs with PDCP duplication(wherein radio conditions may improve if PDCP duplication becomesdeactivated). The base station may allocate more radio resources if aconnection failure occurs without PDCP packet duplication than theamount of radio resources the base station may allocate if a connectionfailure occurs with PDCP packet duplication.

A wireless device may receive (e.g., from a first base station) a packetduplication activation command for duplication of packet dataconvergence protocol (PDCP) packets. The PDCP packets may be associatedwith a first bearer. The first bearer may be a signaling radio bearer.The wireless device may receive (e.g., from the first base station) afirst radio resource control message. The first radio resource controlmessage may comprise one or more PDCP packet duplication configurationparameters. The PDCP packet duplication configuration parameters mayindicate that PDCP packets associated with the first bearer areduplicated. The wireless device may transmit duplicated PDCP packetsassociated with the first bearer. The transmission may be based on thepacket duplication activation command. The wireless device may determinea connection failure. The connection failure may be a radio linkfailure. The connection failure may be a handover failure. Theconnection failure may be associated with a first cell of the first basestation. The connection failure may be determined based on a number ofradio link control retransmissions (e.g., retransmissions of PDCPpackets of the first bearer, original PDCP packets of the first bearer,and/or duplicated PDCP packets of the first bearer). The connectionfailure may be determined based on one or more out-of-sync detections.The connection failure may be determined based on one or more randomaccess failures. The wireless device may determine a second cell of asecond base station. The wireless device may determine to use the secondcell for a radio resource control connection to the second base station.The wireless device may determine to use the second cell based on theconnection failure. The wireless device may determine to transmit (e.g.,to a second base station) a second radio resource control message.

The second radio control message may comprise a radio link failurereport. The radio link failure report may comprise one or moreinformation elements. The one or more information elements may indicatethat PDCP packets were duplicated. The one or more information elementsmay indicate a time (e.g., a time of the connection failure). The radiolink failure report may comprise an indication that PDCP packetduplication was activated. The radio link failure report may comprise anindication that PDCP packet duplication for at least one bearer wasconfigured. The radio link failure report may comprise an indication ofone or more first cell identifiers associated with one or more firstcells. Original PDCP packets of the first bearer may have beentransmitted via the one or more first cells. The radio link failurereport may comprise an indication of one or more second cell identifiersassociated with one or more second cells. Duplicated PDCP packets of thefirst bearer may have been transmitted via the one or more second cells.The one or more first cells may be different from the one or more secondcells. Original PDCP packets of the first bearer may be transmitted viaa first general packet radio service tunneling protocol tunnel.Duplicated PDCP packets of the first bearer may be transmitted via asecond general packet radio service tunneling protocol tunnel.

Base stations may transmit messages between each other. The first basestation may transmit a message to the second base station. The secondbase station may transmit the message to the first base station. Themessage may comprise the radio link failure report. The message maycomprise a first information element of the radio link failure report.The message may comprise one or more radio resource configurationparameters based on the first information element. A handover may beinitiated based on the one or more radio resource configurationparameters. The first base station may initiate the handover to thesecond base station. The second base station may initiate the handoverto the first base station. The one or more radio resource configurationparameters may comprise a radio signal received quality threshold for ahandover trigger. The one or more radio resource configurationparameters may comprise a radio signal received power threshold for ahandover trigger. The one or more radio resource configurationparameters may comprise one or more PDCP duplication configurationparameters. The first base station may configure the one or more radioresource configuration parameters based on the first informationelement.

One or more beams may be managed via one or more of L1 and/or L2procedures. The L1 and/or L2 procedures may be used to acquire and/ormaintain a set of transmission reception points (TRPs) associated with abase station and/or associated with a wireless device. The L1 and/or L2procedures may be used to acquire and/or maintain wireless device beams,which may be used for DL and UL transmission and/or reception. Beammanagement may comprise one or more of: beam determination (e.g., forTRP(s) or a wireless device to select its own Tx/Rx beam(s)), beammeasurement (e.g., for one a TRP(s) or wireless device to measurecharacteristics of received beamformed signals), beam reporting (e.g.,for a wireless device to report information of beamformed signal(s)based on beam measurement), and/or beam sweeping (e.g., using a beam tocover a spatial area, wherein beams may be transmitted and/or receivedduring a time interval based on a predefined configuration).

A TRP and/or a wireless device may select one or more Tx or Rx beamsbased on determined compatibility and/or capability information. A TRPmay select a TRP Rx beam to be used for uplink reception based on awireless device performing a downlink measurement of one or more Txbeams from the TRP. A TRP may select a TRP Tx beam for downlinktransmission based on the TRP performing an uplink measurement of one ormore Rx beams received by the TRP. A wireless device may select a Txbeam for uplink transmission to a TRP based on performing a downlinkmeasurement of one or more Rx beams. A wireless device may select an Rxbeam for receiving communication from a TRP based on an uplinkmeasurement of one or more Tx beams transmitted by the wireless device.

A base station may perform DL L1 and/or L2 beam management proceduresassociated with one or more TRPs. A first beam management procedure mayenable a wireless device to measure one or more TRP Tx beams to supportselection of TRP Tx beam(s) and/or wireless device Rx beam(s).Beamforming may be performed using an intra-TRP and/or an inter-TRP Txbeam sweep from a set of different beams. A wireless device may performbeamforming using a Rx beam sweep from a set of different beams. Asecond beam management procedure may enable a wireless device to measuredifferent TRP Tx beams to configure inter-TRP beam(s) and/or intra-TRPTx beam(s). The second beam management procedure may use a subset oftransmission beams used for the first beam management procedure. A thirdbeam management procedure may enable a wireless device to measure a TRPTx beam to change an Rx beam associated with a wireless device (e.g., abeam used for beamforming). The beam management procedures may supportnetwork-triggered aperiodic beam reporting.

A wireless device measurement for beam management based on a referencesignal (RS), such as a channel state information reference signal(CSI-RS), may be based on a total number of configured beams “K,” and/ora number of selected Tx beams “N.” This measurement may apply towireless devices. Reporting information may include measurementquantities for N beam(s) and information indicating N DL Tx beam(s), ifN<K. If a wireless device is configured with K>1 non-zero power (NZP)CSI-RS resources, a wireless device may report N CSI-RS resourceindicators (CRIs). A wireless device may be configured with multiplereporting settings, and/or multiple resource settings. The reportingsettings and resource settings may be configured via a CSI measurementsetting. Resource and reporting settings may support one or more beammanagement procedures, as discussed above, utilizing CSI-RSs. One ormore beam management procedures may be supported with or withoutreporting setting. A reporting setting may include, for example:information indicating selected beam(s); L1 measurement reporting;time-domain behavior (e.g., aperiodic, periodic, or semi-persistent);and/or frequency-granularity (e.g., if multiple frequency granularitiesare supported). A resource setting may include: time-domain behavior(e.g. aperiodic, periodic, or semi-persistent); RS type (e.g., NZPCSI-RS); and/or at least one CSI-RS resource set. Each CSI-RS resourceset may have K≥1 CSI-RS resources. Some parameters of K CSI-RS resourcesmay be the same (e.g., port number, time-domain behavior, density,and/or periodicity may be the same).

A wireless device may report information about TRP Tx Beam(s) that maybe received using selected wireless device Rx beam set(s). A Rx beam setmay refer to a set of wireless device Rx beams that may be used forreceiving a DL signal. A wireless device may construct the Rx beam setin multiple ways. Each Rx beam in a wireless device Rx beam set maycorrespond to a selected Rx beam in each panel. For wireless deviceswith more than one wireless device Rx beam sets, the wireless device mayreport TRP Tx Beam(s) and an identifier of the associated wirelessdevice Rx beam set for each reported TX beam(s). Different TRP Tx beamsreported for the same Rx beam set may be received simultaneously at thewireless device.

A wireless device may report information about TRP Tx Beam(s) for eachwireless device antenna group, wherein a wireless device antenna groupmay refer to a wireless device receiving antenna panel or subarray. Forwireless devices with more than one wireless device antenna group, thewireless device may report TRP Tx Beam(s) and an identifier of theassociated wireless device antenna group for each reported Tx beam. Thewireless device may simultaneously receive different Tx beams fordifferent antenna groups.

Beam reporting may be performed for a number of “L” groups. Each of theL groups may refer to a Rx beam set or a wireless device antenna group.For each group, a wireless device may report, for example, the followinginformation: information indicating a group; measurement quantities forN beam(s) of L group(s), which may support L1 RSRP and CSI reporting(e.g., when CSI-RS is for CSI acquisition); and/or informationindicating a number of DL Tx beam(s). Group-based beam reporting may beconfigurable for each wireless device. Group-based beam reporting may beturned off independently for each wireless device, such as when a grouponly comprises a single beam. If group-based beam reporting is turnedoff, a group identifier may be excluded.

A wireless device may trigger a mechanism to recover from beam failure.A beam failure event may occur if, for example, the quality of beam pairlink(s) of an associated control channel falls too low (e.g., fallsbelow a threshold), and/or if there is a time-out of an associated timerbefore any transmission is received. A mechanism to recover from beamfailure may be triggered if a beam failure occurs. A wireless device maybe configured with resources for UL transmission of signals for beamfailure recovery. Configurations of resources may be supported whereinthe base station may monitor from all or partial directions (e.g., arandom access region). The UL transmission/resources to report beamfailure may be located in the same time instance as a PRACH (orresources orthogonal to PRACH resources) and/or at a time instance(which may be configurable for a wireless device) different from aPRACH. Transmission of DL signals may support the wireless devicemonitoring beams for identifying newly detected beams.

Beam management may be performed with and without beam-relatedindication. Information pertaining to wireless device-side beamformingand/or receiving procedure used for CSI-RS-based measurement may beindicated through Quasi Co-Location (QCL) to a wireless device, forexample, if beam-related information is provided. The same or differentbeams may be used on a control channel and for corresponding datachannel transmissions.

PDCCH (e.g., NR-PDCCH) transmissions may provide protections againstbeam pair link blocking. A wireless device may be configured to monitorNR-PDCCH on “M” beam pair links simultaneously, wherein M≥1, and whereinthe maximum value of M may be determined based on wireless devicecapability. A wireless device may be configured to monitor NR-PDCCH ondifferent beam pair link(s) in different NR-PDCCH OFDM symbols.Parameters related to wireless device Rx beam setting for monitoringNR-PDCCH on multiple beam pair links may be configured by higher layersignaling, MAC CE, and/or considered in the search space design.Indication of spatial QCL assumption between an DL RS antenna port(s) orDL RS antenna port(s) for demodulation of DL control channel may beprovided. Candidate signaling methods for beam indication correspondingto a NR-PDCCH (such as a configuration method to monitor NR-PDCCH) maybe MAC CE signaling, RRC signaling, DCI signaling,specification-transparent signaling, and/or implicit method signaling.

Indication of spatial QCL assumption between DL RS antenna port(s) andDMRS antenna port(s) of DL data channel (e.g., to support reception of aunicast DL data channel) may be provided. Information indicating the RSantenna port(s) may be indicated via a DCI (e.g., downlink grants). Theinformation may indicate the RS antenna port(s) which may be QCL-ed withDMRS antenna port(s). Different sets of DMRS antenna port(s) for the DLdata channel may be indicated using QCL with different set of RS antennaport(s).

FIG. 15 shows an example of packet duplication and radio link failure(RLF). A wireless device 1501 may receive, from a first base station1505, beam information corresponding to a first cell served by the firstbase station 1505. The wireless device 1501 may be a wireless device406. The first base station 1505 may be a base station 401. One or moreelements of the beam information may be transmitted, from the first basestation 1505 to the wireless device 1501, via, for example: one or morebroadcasted messages, one or more radio resource control (RRC) messages,one or more physical layer signals, etc. Beam information may berecognized by the wireless device 1501 based on one or moresynchronization signals (e.g., SS block) and/or one or more referencesignals (e.g., CSI-RS, DM-RS). The beam information may comprise, forexample, a beam identifier, beam scheduling information, beamconfiguration information, synchronization signal schedulinginformation, synchronization signal sequence information, asynchronization signal block identifier, reference signal schedulinginformation, reference signal configuration information, and/orreference signal block identifier.

Based on one or more elements of the beam information, the wirelessdevice 1501 may receive one or more radio resource control messages viaone or more first beams of the first cell. The one or more first beamsmay be associated with one or more elements of the beam information. Thewireless device 1501 may transmit and/or receive one or more radioresource control messages, and/or one or more data packets based on oneor more of the one or more radio resource control messages, via one ormore of the one or more first beams. The wireless device 1501 may be ina radio resource control connected state (RRC connected state). Thewireless device 1501 may have a radio resource control connection withthe first base station 1505 via the first cell and/or one or more of thefirst beams.

A wireless device 1501 in a radio resource control connected state maydetect a radio link failure from the first cell. The wireless device1501 may determine the radio link failure based on: one or more failureevents of an out-of-sync detection of a physical layer, one or morerandom access failures, a plurality of retransmissions of a radio linkcontrol layer (RLC layer), one or more timer expirations, etc. The oneor more failure events may occur in the first cell and/or one or more ofthe first beams. The radio link failure may be determined separately foreach beam of the one or more first beams. The radio link failure may bedetermined based on detecting multiple beam failures. If the wirelessdevice 1501 detects an out-of-sync in one beam and detects an in-syncconnection via another beam, the wireless device 1501 may determinethere is not a radio link failure. The wireless device 1501 may count anumber of random access failures and/or a number of retransmissions inan RLC layer for each beam separately and/or for multiple beams,collectively. The wireless device 1501 may determine a timer expirationfor one or more beams.

The wireless device, 1501 based on detecting a radio link failure, mayselect a second cell served by a second base station 1510. The secondbase station 1510 may be a base station 401. The second cell may be thefirst cell. Through one or more random access procedures, the wirelessdevice 1501 may establish a radio resource control connection 1515 withthe second base station 1510 via the second cell. The wireless device1501 may establish the radio resource control connection 1515 via: aradio resource control reconfiguration procedure, a radio resourcecontrol reestablishment procedure, and/or a radio resource control setupprocedure. The second base station 1510 may request a radio link failurereport from the wireless device 1501 connected, via the second cell, tothe second base station 1510.

The wireless device 1501 may transmit, to the second base station 1510,a first message comprising a radio link failure report (RLF report) viathe second cell. The radio link failure report may comprise one or moreelements of the beam information received from the first base station1505 via the first cell. The radio link failure report may comprise: oneor more elements of the beam information, a reference signal receivedpower (RSRP), a reference signal received quality (RSRQ), a combinedreference signal received power, and/or a combined reference signalreceived quality. The combined reference signal received quality maycomprise: a beam that the wireless device 1501 recently connected to inthe first cell, one or more beams that the wireless device 1501established a beam pair link with in the first cell, one or more beamsthat the wireless device 1501 attempted to recover a beam pair linkwith, one or more beams that the first base station 1505 assigned to thewireless device 1501, one or more beams that the wireless device 1501attempted to use in a random access connection, one or more neighboringbeams, etc. The first message may further comprise one or more networkslice identifiers of one or more network slices served from the firstbase station 1505 to the wireless device 1501.

The combined reference signal received power may be determined bycombining one or more reference signal received powers of one or morebeams (e.g., averaging one or more RSRPs of one or more beams), and/orby combining one or more reference signal received qualities of one ormore beams (e.g., averaging one or more RSRQs of one or more beams).

The radio link failure report may comprise, for example: a radio linkfailure cause (e.g., one or more timer expiration, t310-Expiry,t312-Expiry, a random access problem, a maximum number of RLC layerretransmissions, etc.), a failed primary cell identifier, a recentserving cell RSRQ type, a recent serving beam RSRQ type, one or moremeasurement result for one or more beams and/or one or more cells, areestablishment cell identifier, beam information associated with one ormore beams of a reestablishment cell, a previous primary cellidentifier, etc. The radio link failure report may comprise informationregarding whether an RSRP and/or an RSRQ of one or more beams and/or oneor more cells was measured based on a synchronization signal (e.g., SSblock) or based on a reference signal (e.g., CSI-RS, DM-RS). The radiolink failure report may comprise a cell quality information of arecently connected cell, a recent serving cell, a failed primary cell,and/or one or more neighboring cells. The cell quality information maybe determined, for example, by combining one or more RSRPs of one ormore beams and/or by combining one or more RSRQs of one or more beams.The radio link failure report may comprise a number of beams consideredto determine a cell quality of: the first cell, one or more other recentserving cells, and/or one or more recent neighboring cells.

The radio link failure report may comprise information regarding whetherone or more failed random access attempts was a 2-stage random accessattempt or a 4-stage random access attempt. The radio link failurereport may comprise information regarding whether one or more failedrandom access attempts was a contention-free random access attempt or acontention-based random access attempt. The radio link failure reportmay comprise a number of beams used by the wireless device for attemptedrandom access.

The radio link failure report may comprise: beam information of one ormore target beams for a failed handover, beam information of one or moreserving beams for a failed handover, beam information associated withone or more recently connected beams of a recently connected cellassociated with a failed handover, and/or beam information of one ormore neighboring beams of a neighbor cell for a failed handover. Theradio link failure report may comprise: a reference signal receivedpower (RSRP) of a target beam of a target cell associated with a failedhandover, a reference signal received quality (RSRQ) of a target beam ofa target cell associated with a failed handover, a combined referencesignal received power of one or more target beams of a target cellassociated with a failed handover, and/or a combined reference signalreceived quality of one or more target beams of a target cell for afailed handover. The radio link failure report may comprise an RSRP of aneighboring beam of a neighboring cell associated with a failedhandover, an RSRQ of a neighboring beam of a neighboring cell associatedwith a failed handover, a combined reference signal received power ofone or more neighboring beams of a neighboring cell associated with afailed handover, and/or a combined reference signal received quality ofone or more neighboring beams of a neighboring cell associated with afailed handover.

The radio link failure report may comprise an RSRP and/or an RSRQ of aserving beam associated with a failed handover. The radio link failurereport may comprise a combined reference signal received power and/or acombined reference signal received quality of one or more serving beamsassociated with a failed handover. The radio link failure report maycomprise an RSRP and/or an RSRQ of a recently connected beam of a lastconnected cell associated with a failed handover. The radio link failurereport may comprise a combined reference signal received power and/or acombined reference signal received quality of one or more recentlyconnected beams of a recently connected cell associated with a failedhandover.

The second base station 1510 that receives the first message from thewireless device 1501 may transmit one or more elements of the firstmessage to the first base station 1505. Based on receiving the one ormore elements of the first message, the first base station 1505 mayconfigure one or more system control parameters based on the one or moreelements of the first message. The one or more system control parametersmay comprise one or more beam configuration parameters, one or moreradio resource power parameters, one or more random access resourceparameters, one or more mobility parameters, a radio signal receivedquality threshold for initiating a handover, a radio signal receivedpower threshold for initiating a handover, etc. The first base station1505 may initiate a wireless device handover based on the one or moresystem control parameters, wherein the one or more system controlparameters may be based on the one or more elements of the firstmessage. The first base station 1505 may configure one or more mobilityparameters for the wireless device 1501 with one or more network slicesbased on the one or more elements of the first message.

The first base station 1505 may transmit a command for configurationand/or activation of duplication of Packet Data Convergence Protocol(PDCP) packets 1530 associated with a bearer (e.g., a signaling radiobearer or a data radio bearer) for a wireless device 1501. DuplicatedPDCP packets 1525 may be transmitted via different cells from cellsemployed to transmit original PDCP packets. The duplicated PDCP packets1525 may be transmitted using a general packet radio service tunnelingprotocol (GTP) tunnel that may be different from a general packet radioservice tunneling protocol (GTP) tunnel used for original PDCP packets.PDCP packet duplication may decrease the risk of radio link failuresbecause of diversity gain of packet transmissions. The wireless device1501 may provide, to the first base station 1505 or a new base station(e.g., the second base station 1510), a radio link failure report 1520indicating that PDCP packets for a bearer were duplicated in a previousRadio Resource Control (RRC) connection to one or more previouslyconnected base stations in which the wireless device experienced a RadioLink Failure (RLF) and/or a Handover Failure (HOF).

A wireless device 1501 that experiences an RLF and/or a HOF may try tomake an RRC connection to the first cell or a new cell. If the wirelessdevice 1501 establishes (or reestablishes) an RRC connection to the newcell, the wireless device 1501 may transmit an RLF report to a basestation serving the new cell (e.g., the second base station 1510). Thebase station (e.g., the second base station 1510) may send informationof the radio link failure of the wireless device 1501 to an old basestation (e.g., the first base station 1505) where the wireless device1501 experienced the RLF (and/or the HOF) and/or where a mobilityprocedure that caused the radio link failure (and/or the HOF) wasinitiated. The old base station (e.g., the first base station 1505)receiving the information of the radio link failure for the wirelessdevice 1501 may analyze a reason of the radio link failure and/or mayreconfigure one or more configuration parameters and/or mobilitysettings for initiating a handover. The above may have the advantage ofenabling a base station to analyze the radio link failure and/or toreconfigure mobility settings with respect to configuration of PDCPpacket duplication based on the information of the RLF of the wirelessdevice 1501.

FIG. 16 shows an example message flow associated with RLF. A firstwireless device 1601 (which may be the wireless device 1501) mayreceive, from a first base station 1605 (which may be the first basestation 1505), a first Radio Resource Control (RRC) message 1615. Thefirst RRC message 1615 may be an RRC connection reconfiguration message,an RRC connection reestablishment message, an RRC connection setupmessage, an RRC connection resume message, etc. The first RRC message1615 may comprise bearer configuration information of one or morebearers (e.g., a signaling radio bearer, a data radio bearer, a logicalchannel, a QoS flow, a PDCU session, etc.). The first RRC message 1615may comprise a Packet Data Convergence Protocol (PDCP) packetduplication indication 1620 indicating that one or more PDCP packetsassociated with a first bearer are duplicated, and/or that original PDCPpackets and duplicated PDCP packets may be transmitted independently.Original PDCP packets of the one or more PDCP packets may be transmittedvia one or more cells different from one or more other cells via whichduplicated PDCP packets are transmitted. The one or more cells and/orthe one or more other cells may be served by the first base station 1605and/or a second base station 1610 (which may be the second base station1510) for the first wireless device 1601. The second base station 1610may be a secondary base station.

PDCP packets associated with the first bearer may be duplicated one ormore times. The first bearer may be mapped to an original logicalchannel (and/or an original GTP tunnel) and/or multiple duplicatedlogical channels (and/or multiple GTP tunnels). Some portion of PDCPpackets associated with the first bearer may be duplicated andtransmitted separately from original PDCP packets. An amount of the someportion may be configured by the first base station 1605 and/or thesecond base station 1610 for the first wireless device 1601 via thefirst RRC message 1615 and/or via a Medium Access Control ControlElement (MAC CE) message. The amount of the some portion may be between0% and 100% of original PDCP packets.

The first bearer may be a Signaling Radio Bearer (SRB) associated withcontrol plane signaling transmissions. The first wireless device 1601and/or the first base station 1605 may determine an RLF (and/or an HOF)when a number of Radio Link Control (RLC) layer packet retransmissionsassociated with the first bearer reaches a threshold value. If a numberof RLC layer packet retransmissions associated with original PDCPpackets of the first bearer reaches the threshold value, the firstwireless device 1601 and/or the first base station 1605 may determine anRLF (and/or an HOF). If a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer reaches thethreshold value, the first wireless device 1601 and/or the first basestation 1605 may determine an RLF (and/or an HOF).

The first wireless device 1601 may receive, from the first base station1605, a first MAC CE message comprising a PDCP packet duplicationactivation request 1625 (which may be a request, a command or anindication) for the wireless device to begin transmitting duplicatedPDCP packets. Based on the first MAC CE message, the first wirelessdevice 1601 may transmit, to a device (e.g., the first base station1605, the second base station 1610 for the first wireless device 1601,one or more other wireless devices, etc.), one or more duplicated PDCPpackets associated with the first bearer at least based on the PDCPpacket duplication indication. The first RRC message 1615 may comprisean indication of initiating or stopping (e.g., activating ordeactivating) transmission of duplicated PDCP packets associated withthe PDCP packet duplication indication.

The first wireless device 1601 may receive, from the first base station1605, a second MAC CE message comprising a request for the wirelessdevice to cease transmitting duplicated PDCP packets associated with thePDCP packet duplication indication. Based on the second MAC CE message,the first wireless device 1601 may stop transmitting (e.g., to the firstbase station 1605, to the second base station 1610, to one or more otherwireless devices, etc.) duplicated PDCP packets associated with thefirst bearer based on the PDCP packet duplication indication.

At step 1630, the first wireless device 1601 may determine a connectionfailure associated with one or more first cells of the first basestation 1605 (and/or the second base station 1610 for the first wirelessdevice 1601). The connection failure may be an RLF and/or an HOF. Theconnection failure may be determined based on: a number of RLC packetretransmissions, out-of-sync detection, one or more random accessfailures, etc. The first wireless device 1601 may determine an RLF(and/or an HOF) if a number of Radio Link Control (RLC) layer packetretransmissions associated with the first bearer exceeds (or meets) athreshold value. If a number of RLC layer packet retransmissionsassociated with original PDCP packets and/or duplicated PDCP packets ofthe first bearer exceeds (or meets) a threshold value, the firstwireless device 1601 may determine an RLF (and/or an HOF).

If a device (e.g., a base station and/or a wireless device) detects thata number of RLC layer packet retransmissions associated with originalPDCP packets of the first bearer exceeds (or meets) a threshold value,the device may report the detection from an RLC layer to an RRC layer.If the device detects that a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer exceeds (ormeets) a threshold value, the device may report the detection from anRLC layer to an RRC layer. The device (e.g., at an RRC layer) maydetermine an RLF (and/or an HOF) based on the received reports from RLClayer. The device (e.g., at an RRC layer) may determine an RLF (and/oran HOF) if it receives the report indicating that a number of RLC layerpacket retransmissions associated with original PDCP packets of thefirst bearer exceeds (or meets) a threshold value. The device (e.g., atan RRC layer) may determine an RLF (and/or an HOF) if it receives thereport indicating that a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer exceeds (ormeets) a threshold value. The device (e.g., at an RRC layer) maydetermine an RLF (and/or an HOF) if it receives both a first report anda second report, wherein the first report indicates that a number of RLClayer packet retransmissions associated with original PDCP packets ofthe first bearer exceeds (or meets) a threshold value, and a secondreport indicates that a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer exceeds (ormeets) a threshold value.

The first wireless device 1601, based on determining a connectionfailure, may select a second cell of a second base station 1610 for anRRC connection to the second base station 1610 at step 1635. The secondcell may be one of the one or more first cells of the first base station1605 and/or the second base station 1610. The first wireless device 1601may select the second cell based on a reference signal received power(RSRP) and/or a reference signal received quality (RSRQ) of the secondcell.

Based on selecting the second cell for an RRC connection to the secondbase station 1610, the first wireless device 1601 may initiate a randomaccess (RA) procedure 1640, via the second cell, by transmitting, viathe second cell, one or more random access preambles. In performing theRA procedure 1640, the first wireless device 1601 may transmit a secondRRC message to the second base station 1610 via the second cell. Thesecond RRC message may comprise, for example, one or more of: an RRCconnection reestablishment request message, an RRC connection requestmessage, an RRC connection resume request message, an RRC connectionreestablishment complete message, an RRC connection setup completemessage, an RRC connection resume complete message, an RLF informationavailability indication 1650, and/or an RLF report 1645. The RLFinformation availability indication 1650 may indicate that the firstwireless device 1601 has RLF information and/or HOF information. Basedon the connection failure, the first wireless device 1601 may indicatethat the first wireless device 1601 has RLF information and/or HOFinformation via the RLF information availability indication to thesecond base station 1610.

Based on the second RRC message and/or completion of the RA procedure,the first wireless device 1601 may receive a request message from thesecond base station 1610. This may occur as part of the RA procedure1640 (e.g., the request message may be an RRC message associated with RAprocedure 1640). The request message may comprise one or more of awireless device information request message and/or an RLF report requestconfigured to request an RLF report for an RLF and/or an HOF.

Based on the request message received from the second base station 1610and/or based on the second RRC message and/or completion of the RAprocedure 1640, the first wireless device 1601 may transmit a reportmessage 1645. The report message 1645 may comprise one or more of awireless device information response message, and/or an RLF report.

The RLF report of the second RRC message and/or of the report messagemay comprise PDCP packet duplication information associated with theprevious RRC connection (e.g., a previous RRC connection associated withthe first base station 1605 and/or the second base station 1610 for thefirst wireless device 1601). The PDCP packet duplication information maycomprise, for example: a PDCP packet duplication activation indication,a PDCP packet duplication configuration indication, a bearer identifierof the first bearer, a bearer type of the first bearer (e.g., SRB0,SRB1, SRB2, data radio bearer, etc.), a number of bearers thatconfigured for PDCP packet duplication, one or more logical channelidentifiers of one or more logical channels associated with duplicatedPDCP packets and/or original packets, a duplicated portion of a PDCPpacket duplication, a number of duplications, an RLF cause, one or morecell identifiers of one or more cells employed to transmit original PDCPpackets, one or more cell identifiers of one or more cells employed totransmit duplicated PDCP packets, one or more base station identifiersof one or more base stations employed to transmit original PDCP packets(e.g., a base station identifier of the first base station 1605 and/orthe second base station 1610 for the first wireless device 1601), one ormore base station identifiers of one or more base stations employed totransmit duplicated PDCP packets (e.g., a base station identifier of thefirst base station 1605 and/or the second base station 1610 for thefirst wireless device 1601), etc.

The PDCP packet duplication activation indication may be configured toindicate that one or more bearers (e.g., the first bearer, one or moreSRBs, one or more DRBs, etc.) have been configured for PDCP packetduplication by the first base station 1605 via the first MAC CE messageand/or via the first RRC message (e.g., before the time of theconnection failure). The PDCP packet duplication configurationindication may be configured to indicate that a PDCP packet duplicationfor one or more bearers (e.g., the first bearer, one or more SRBs, oneor more DRBs, etc.) was configured by the first base station 1605 viathe first RRC message (e.g., before the time of the connection failure).The PDCP packet duplication configuration indication may be configuredto indicate that duplicated PDCP packets for one or more bearers (e.g.,the first bearer, one or more SRBs, one or more DRBs, etc.) were beingtransmitted at the time of the connection failure.

The number of bearers configured for PDCP packet duplication mayindicate a number of bearers that were duplicated. The number may be 1,for example, if only the first bearer was duplicated. The number may belarger than 1, for example, if one or more bearers other than the firstbearer were configured and/or activated for PDCP packet duplication.

The duplicated portion of a duplicated PDCP packet may be configured toindicate how much portion of original PDCP packets were duplicated forthe first bearer. The duplicated portion of a duplicated PDCP packet maybe a value between 0% and 100%.

The number of duplications may indicate how many duplications wereconfigured and/or activated for PDCP packets associated with the firstbearer. The number of duplications may indicate how many logicalchannels (e.g., one logical channel for original PDCP packets, and/orone or more logical channels for one or more duplications of originalPDCP packets) for PDCP packets were mapped (e.g., configured and/oractivated) for the first bearer.

The RLF cause may indicate that a reason of the connection failure wasone or more of a number of RLC packet retransmissions (e.g., a number ofRLC packet retransmissions exceeds a threshold value), one or moreout-of-sync detection indications (e.g., an RRC layer receives, from alower layer, one or more out-of-sync detection indication, and/or thesynchronization was not recovered within a threshold time duration), oneor more random access failures (e.g. the first wireless device failed inone or more random access attempts), etc.

Based on receiving the RLF report, the second base station 1610 maysend, to the first base station 1605, a message 1650 comprising one ormore elements of the RLF report. The one or more elements may be sentdirectly or indirectly (e.g., via direct interface such as X2 interfaceor Xn interface, and/or via core network entity such as MME and/or AMF).The one or more elements of the RLF report may be sent via a handoverreport message and/or via an RLF indication message. The first basestation 1605 may configure one or more control parameters based on theone or more elements of the RLF report. The one or more controlparameters may comprise one or more handover parameters (e.g., a radiosignal received quality threshold, a radio signal received powerthreshold for a handover initiation, etc.), one or more PDCP packetduplication configuration parameters for one or more bearers of one ormore wireless devices, and/or other radio configuration parametersassociated with one or more cells and/or one or more wireless devices.

If PDCP packet duplication for an SRB of a first wireless device 1601was not configured and/or was not activated at the time of theconnection failure, a first base station 1605 may configure and/oractivate an SRB of another wireless device that has similar radio signalmeasurement results to the first wireless device 1601.

The first base station 1605 may initiate a handover of a second wirelessdevice based on the one or more control parameters. The one or morecontrol parameters may be configured based on the one or more elementsof the RLF report. If PDCP packet duplication for an SRB of the firstwireless device 1601 was configured and/or activated at the time of theconnection failure of the first wireless device 1601, the first basestation 1605 may initiate a handover for the second wireless deviceearlier than for the first wireless device 1601 (e.g., if the first basestation 1605 configured and/or activated a PDCP packet duplication foran SRB of the second wireless device).

A first wireless device 1601 may receive, from a first base station1605, a first Radio Resource Control (RRC) message comprising a PacketData Convergence Protocol (PDCP) packet duplication indicationindicating that a plurality of PDCP packets associated with a firstbearer are duplicated. The first wireless device 1601 may receive aMedium Access Control Control Element (MAC CE) message indicating anactivation of transmitting duplicated PDCP packets associated with thePDCP packet duplication indication. The first wireless device 1601 maytransmit one or more duplicated packets associated with the first bearerbased on the PDCP packet duplication indication and/or the MAC CEmessage. The first wireless device 1601 may determine a connectionfailure from a first cell of the first base station 1605. The firstwireless device 1601 may select a second cell of a second base station1610 for an RRC connection to the second base station 1610 based on theconnection failure. The first wireless device 1601 may transmit, to thesecond base station 1610 via the second cell, a second RRC messagecomprising a Radio Link Failure (RLF) report associated with theconnection failure, wherein the RLF report may comprise PDCP packetduplication information indicating one or more of: activation of aduplicated PDCP packet transmission; and/or configuration of PDCP packetduplication for at least one bearer.

The first base station 1605 may receive, from the second base station1610, one or more elements of the RLF report. The first base station1605 may configure one or more control parameters based on the one ormore elements of the RLF report. The first base station 1605 mayinitiate a handover of a second wireless device based on the one or morecontrol parameters. The one or more control parameters may comprise oneor more of a radio signal received quality threshold or a radio signalreceived power threshold for a handover initiation. The one or morecontrol parameters may comprise one or more PDCP duplicationconfiguration parameters for one or more bearers of one or more wirelessdevices.

The connection failure may be one or more of a radio link failure and/ora handover failure. The first base station 1605 may be the second basestation 1610. The first cell may be the second cell. The RLF report maycomprise one or more cell identifiers of one or more cells (e.g., one ormore cells via which the duplicated plurality of PDCP packets of atleast one bearer were transmitted). The first bearer may be a SignalingRadio Bearer (SRB). The determination of the connection failure may bebased on a number of RLC retransmissions of one or more packetsassociated with: original PDCP packets of the first bearer; and/orduplicated PDCP packets of the first bearer. The determination of theconnection failure may be based on: a number of RLC retransmissions; oneor more out-of-sync detections; and/or one or more random accessfailures.

FIG. 17 shows an example of packet duplication and radio link failure(RLF). A wireless device 1701 may receive, from a first base station1705, beam information corresponding to a first cell served by the firstbase station 1705. The wireless device 1701 may be a wireless device406. The first base station 1705 may be a base station 401. One or moreelements of the beam information may be transmitted, from the first basestation 1705 to the wireless device 1701, via, for example: one or morebroadcasted messages, one or more radio resource control (RRC) messages,one or more physical layer signals, etc. Beam information may berecognized by the wireless device 1701 based on one or moresynchronization signals (e.g., SS block) and/or one or more referencesignals (e.g., CSI-RS, DM-RS). The beam information may comprise, forexample, a beam identifier, beam scheduling information, beamconfiguration information, synchronization signal schedulinginformation, synchronization signal sequence information, asynchronization signal block identifier, reference signal schedulinginformation, reference signal configuration information, and/orreference signal block identifier.

Based on one or more elements of the beam information, the wirelessdevice 1701 may receive one or more radio resource control messages viaone or more first beams of the first cell. The one or more first beamsmay be associated with one or more elements of the beam information. Thewireless device 1701 may transmit and/or receive one or more radioresource control messages, and/or one or more data packets based on oneor more of the one or more radio resource control messages, via one ormore of the one or more first beams. The wireless device 1701 may be ina radio resource control connected state (RRC connected state). Thewireless device 1701 may have a radio resource control connection withthe first base station 1705 via the first cell and/or one or more of thefirst beams.

A wireless device 1701 in a radio resource control connected state maydetect a radio link failure from the first cell. The wireless device1701 may determine the radio link failure based on: one or more failureevents of an out-of-sync detection of a physical layer, one or morerandom access failures, a plurality of retransmissions of a radio linkcontrol layer (RLC layer), one or more timer expirations, etc. The oneor more failure events may occur in the first cell and/or one or more ofthe first beams. The radio link failure may be determined separately foreach beam of the one or more first beams. The radio link failure may bedetermined based on detecting multiple beam failures. If the wirelessdevice 1701 detects an out-of-sync in one beam and detects an in-syncconnection via another beam, the wireless device 1701 may determinethere is not a radio link failure. The wireless device 1701 may count anumber of random access failures and/or a number of retransmissions inan RLC layer for each beam separately and/or for multiple beams,collectively. The wireless device 1701 may determine a timer expirationfor one or more beams.

The wireless device, 1701 based on detecting a radio link failure, mayselect a second cell served by the first base station 1705. The firstbase station 1705 may be a base station 401. The second cell may be thefirst cell. Through one or more random access procedures, the wirelessdevice 1701 may establish a radio resource control connection 1715 withthe first base station 1705 via the second cell. The wireless device1701 may establish the radio resource control connection 1715 via: aradio resource control reconfiguration procedure, a radio resourcecontrol reestablishment procedure, and/or a radio resource control setupprocedure. The first base station 1705 may request a radio link failurereport from the wireless device 1701 connected, via the second cell, tothe first base station 1705.

The wireless device 1701 may transmit, to the first base station 1705, afirst message comprising a radio link failure report (RLF report) viathe second cell. The radio link failure report may comprise one or moreelements of the beam information received from the first base station1705 via the first cell. The radio link failure report may comprise: oneor more elements of the beam information, a reference signal receivedpower (RSRP), a reference signal received quality (RSRQ), a combinedreference signal received power, and/or a combined reference signalreceived quality. The combined reference signal received quality maycomprise: a beam that the wireless device 1701 recently connected to inthe first cell, one or more beams that the wireless device 1701established a beam pair link with in the first cell, one or more beamsthat the wireless device 1701 attempted to recover a beam pair linkwith, one or more beams that the first base station 1705 assigned to thewireless device 1701, one or more beams that the wireless device 1701attempted to use in a random access connection, one or more neighboringbeams, etc. The first message may further comprise one or more networkslice identifiers of one or more network slices served from the firstbase station 1705 to the wireless device 1701.

The combined reference signal received power may be determined bycombining one or more reference signal received powers of one or morebeams (e.g., averaging one or more RSRPs of one or more beams), and/orby combining one or more reference signal received qualities of one ormore beams (e.g., averaging one or more RSRQs of one or more beams).

The radio link failure report may comprise, for example: a radio linkfailure cause (e.g., one or more timer expiration, t310-Expiry,t312-Expiry, a random access problem, a maximum number of RLC layerretransmissions, etc.), a failed primary cell identifier, a recentserving cell RSRQ type, a recent serving beam RSRQ type, one or moremeasurement result for one or more beams and/or one or more cells, areestablishment cell identifier, beam information associated with one ormore beams of a reestablishment cell, a previous primary cellidentifier, etc. The radio link failure report may comprise informationregarding whether an RSRP and/or an RSRQ of one or more beams and/or oneor more cells was measured based on a synchronization signal (e.g., SSblock) or based on a reference signal (e.g., CSI-RS, DM-RS). The radiolink failure report may comprise a cell quality information of arecently connected cell, a recent serving cell, a failed primary cell,and/or one or more neighboring cells. The cell quality information maybe determined, for example, by combining one or more RSRPs of one ormore beams and/or by combining one or more RSRQs of one or more beams.The radio link failure report may comprise a number of beams consideredto determine a cell quality of: the first cell, one or more other recentserving cells, and/or one or more recent neighboring cells.

The radio link failure report may comprise information regarding whetherone or more failed random access attempts was a 2-stage random accessattempt or a 4-stage random access attempt. The radio link failurereport may comprise information regarding whether one or more failedrandom access attempts was a contention-free random access attempt or acontention-based random access attempt. The radio link failure reportmay comprise a number of beams used by the wireless device for attemptedrandom access.

The radio link failure report may comprise: beam information of one ormore target beams for a failed handover, beam information of one or moreserving beams for a failed handover, beam information associated withone or more recently connected beams of a recently connected cellassociated with a failed handover, and/or beam information of one ormore neighboring beams of a neighbor cell for a failed handover. Theradio link failure report may comprise: a reference signal receivedpower (RSRP) of a target beam of a target cell associated with a failedhandover, a reference signal received quality (RSRQ) of a target beam ofa target cell associated with a failed handover, a combined referencesignal received power of one or more target beams of a target cellassociated with a failed handover, and/or a combined reference signalreceived quality of one or more target beams of a target cell for afailed handover. The radio link failure report may comprise an RSRP of aneighboring beam of a neighboring cell associated with a failedhandover, an RSRQ of a neighboring beam of a neighboring cell associatedwith a failed handover, a combined reference signal received power ofone or more neighboring beams of a neighboring cell associated with afailed handover, and/or a combined reference signal received quality ofone or more neighboring beams of a neighboring cell associated with afailed handover.

The radio link failure report may comprise an RSRP and/or an RSRQ of aserving beam associated with a failed handover. The radio link failurereport may comprise a combined reference signal received power and/or acombined reference signal received quality of one or more serving beamsassociated with a failed handover. The radio link failure report maycomprise an RSRP and/or an RSRQ of a recently connected beam of a lastconnected cell associated with a failed handover. The radio link failurereport may comprise a combined reference signal received power and/or acombined reference signal received quality of one or more recentlyconnected beams of a recently connected cell associated with a failedhandover.

The first base station 1705 may configure one or more system controlparameters based on the one or more elements of information of the RLF.The one or more system control parameters may comprise one or more beamconfiguration parameters, one or more radio resource power parameters,one or more random access resource parameters, one or more mobilityparameters, a radio signal received quality threshold for initiating ahandover, a radio signal received power threshold for initiating ahandover, etc. The first base station 1705 may initiate a wirelessdevice handover based on the one or more system control parameters,wherein the one or more system control parameters may be based on theone or more elements of the first message. The first base station mayconfigure one or more mobility parameters for the wireless device 1701with one or more network slices based on the one or more elements of thefirst message.

The first base station 1705 may transmit a command for configurationand/or activation of duplication of Packet Data Convergence Protocol(PDCP) packets 1730 associated with a bearer (e.g., a signaling radiobearer or a data radio bearer) for a wireless device 1701. DuplicatedPDCP packets 1725 may be transmitted via different cells from cellsemployed to transmit original PDCP packets. The duplicated PDCP packets1725 may be transmitted using a general packet radio service tunnelingprotocol (GTP) tunnel that may be different from a general packet radioservice tunneling protocol (GTP) tunnel used for original PDCP packets.PDCP packet duplication may decrease the risk of radio link failuresbecause of diversity gain of packet transmissions. The wireless device1701 may provide, to the first base station 1705 or a new base station(e.g., the first base station 1705), a radio link failure report 1720indicating that PDCP packets for a bearer were duplicated in a previousRadio Resource Control (RRC) connection to one or more previouslyconnected base stations in which the wireless device experienced a RadioLink Failure (RLF) and/or a Handover Failure (HOF).

A wireless device 1701 that experiences an RLF and/or a HOF may try tomake an RRC connection to the first cell or a new cell. If the wirelessdevice 1701 establishes (or reestablishes) an RRC connection to the newcell, the wireless device 1701 may transmit an RLF report to a basestation serving the new cell (e.g., the first base station 1705). Thebase station (e.g., the first base station 1705) may send information ofthe radio link failure of the wireless device 1701 to an old basestation (e.g., the first base station 1705) where the wireless device1701 experienced the RLF (and/or the HOF) and/or where a mobilityprocedure that caused the radio link failure (and/or the HOF) wasinitiated. The old base station (e.g., the first base station 1705)receiving the information of the radio link failure for the wirelessdevice 1701 may analyze a reason of the radio link failure and/or mayreconfigure one or more configuration parameters and/or mobilitysettings for initiating a handover. The above may have the advantage ofenabling a base station to analyze the radio link failure and/or toreconfigure mobility settings with respect to configuration of PDCPpacket duplication based on the information of the RLF of the wirelessdevice 1701. The procedures and/or messages of FIG. 17 for a single basestation may comprise some or all of those of, for example, FIG. 15 formultiple base stations.

FIG. 18 shows an example message flow associated with RLF. A firstwireless device 1801 (which may be the wireless device 1701) mayreceive, from a first base station 1805 (which may be the first basestation 1705), a first Radio Resource Control (RRC) message 1815. Thefirst RRC message 1815 may be an RRC connection reconfiguration message,an RRC connection reestablishment message, an RRC connection setupmessage, an RRC connection resume message, etc. The first RRC message1815 may comprise bearer configuration information of one or morebearers (e.g., a signaling radio bearer, a data radio bearer, a logicalchannel, a QoS flow, a PDCU session, etc.). The first RRC message 1815may comprise a Packet Data Convergence Protocol (PDCP) packetduplication indication 1820 indicating that one or more PDCP packetsassociated with a first bearer are duplicated, and/or that original PDCPpackets and duplicated PDCP packets may be transmitted independently.Original PDCP packets of the one or more PDCP packets may be transmittedvia one or more cells different from one or more other cells via whichduplicated PDCP packets are transmitted. The one or more cells and/orthe one or more other cells may be served by the first base station 1805and/or a second base station 1810 (which may be the first base station1705) for the first wireless device 1801. The first base station 1805may be a secondary base station.

PDCP packets associated with the first bearer may be duplicated one ormore times. The first bearer may be mapped to an original logicalchannel (and/or an original GTP tunnel) and/or multiple duplicatedlogical channels (and/or multiple GTP tunnels). Some portion of PDCPpackets associated with the first bearer may be duplicated andtransmitted separately from original PDCP packets. An amount of the someportion may be configured by the first base station 1805 and/or thefirst base station 1805 for the first wireless device 1801 via the firstRRC message 1815 and/or via a Medium Access Control Control Element (MACCE) message. The amount of the some portion may be between 0% and 100%of original PDCP packets.

The first bearer may be a Signaling Radio Bearer (SRB) associated withcontrol plane signaling transmissions. The first wireless device 1801and/or the first base station 1805 may determine an RLF (and/or an HOF)when a number of Radio Link Control (RLC) layer packet retransmissionsassociated with the first bearer reaches a threshold value. If a numberof RLC layer packet retransmissions associated with original PDCPpackets of the first bearer reaches the threshold value, the firstwireless device 1801 and/or the first base station 1805 may determine anRLF (and/or an HOF). If a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer reaches thethreshold value, the first wireless device 1801 and/or the first basestation 1805 may determine an RLF (and/or an HOF).

The first wireless device 1801 may receive, from the first base station1805, a first MAC CE message comprising a PDCP packet duplicationactivation request 1825 (which may be a request, a command or anindication) for the wireless device to begin transmitting duplicatedPDCP packets. Based on the first MAC CE message, the first wirelessdevice 1801 may transmit, to a device (e.g., the first base station 1805and/or one or more other wireless devices, etc.), one or more duplicatedPDCP packets associated with the first bearer at least based on the PDCPpacket duplication indication. The first RRC message 1815 may comprisean indication of initiating or stopping (e.g., activating ordeactivating) transmission of duplicated PDCP packets associated withthe PDCP packet duplication indication.

The first wireless device 1801 may receive, from the first base station1805, a second MAC CE message comprising a request for the wirelessdevice to cease transmitting duplicated PDCP packets associated with thePDCP packet duplication indication. Based on the second MAC CE message,the first wireless device 1801 may stop transmitting (e.g., to the firstbase station 1805 and/or to one or more other wireless devices, etc.)duplicated PDCP packets associated with the first bearer based on thePDCP packet duplication indication.

At step 1830, the first wireless device 1801 may determine a connectionfailure associated with one or more first cells of the first basestation 1805. The connection failure may be an RLF and/or an HOF. Theconnection failure may be determined based on: a number of RLC packetretransmissions, out-of-sync detection, one or more random accessfailures, etc. The first wireless device 1801 may determine an RLF(and/or an HOF) if a number of Radio Link Control (RLC) layer packetretransmissions associated with the first bearer exceeds (or meets) athreshold value. If a number of RLC layer packet retransmissionsassociated with original PDCP packets and/or duplicated PDCP packets ofthe first bearer exceeds (or meets) a threshold value, the firstwireless device 1801 may determine an RLF (and/or an HOF).

If a device (e.g., a base station and/or a wireless device) detects thata number of RLC layer packet retransmissions associated with originalPDCP packets of the first bearer exceeds (or meets) a threshold value,the device may report the detection from an RLC layer to an RRC layer.If the device detects that a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer exceeds (ormeets) a threshold value, the device may report the detection from anRLC layer to an RRC layer. The device (e.g., at an RRC layer) maydetermine an RLF (and/or an HOF) based on the received reports from RLClayer. The device (e.g., at an RRC layer) may determine an RLF (and/oran HOF) if it receives the report indicating that a number of RLC layerpacket retransmissions associated with original PDCP packets of thefirst bearer exceeds (or meets) a threshold value. The device (e.g., atan RRC layer) may determine an RLF (and/or an HOF) if it receives thereport indicating that a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer exceeds (ormeets) a threshold value. The device (e.g., at an RRC layer) maydetermine an RLF (and/or an HOF) if it receives both a first report anda second report, wherein the first report indicates that a number of RLClayer packet retransmissions associated with original PDCP packets ofthe first bearer exceeds (or meets) a threshold value, and a secondreport indicates that a number of RLC layer packet retransmissionsassociated with duplicated PDCP packets of the first bearer exceeds (ormeets) a threshold value.

The first wireless device 1801, based on determining a connectionfailure, may select a second cell of the first base station 1805 for anRRC connection at step 1835. The second cell may be one of the one ormore first cells of the first base station 1805. The first wirelessdevice 1801 may select the second cell based on a reference signalreceived power (RSRP) and/or a reference signal received quality (RSRQ)of the second cell.

Based on selecting the second cell for an RRC connection to the firstbase station 1805, the first wireless device 1801 may initiate a randomaccess (RA) procedure 1840, via the second cell, by transmitting, viathe second cell, one or more random access preambles. In performing theRA procedure 1840, the first wireless device 1801 may transmit a secondRRC message to the first base station 1805 via the second cell. Thesecond RRC message may comprise, for example, one or more of: an RRCconnection reestablishment request message, an RRC connection requestmessage, an RRC connection resume request message, an RRC connectionreestablishment complete message, an RRC connection setup completemessage, an RRC connection resume complete message, an RLF informationavailability indication, and/or an RLF report 1845. The RLF informationavailability indication may indicate that the first wireless device 1801has RLF information and/or HOF information. Based on the connectionfailure, the first wireless device 1801 may indicate that the firstwireless device 1801 has RLF information and/or HOF information via theRLF information availability indication to the first base station 1805.

Based on the second RRC message and/or completion of the RA procedure,the first wireless device 1801 may receive a request message from thefirst base station 1805. This may occur as part of the RA procedure 1840(e.g., the request message may be an RRC message associated with RAprocedure 1840). The request message may comprise one or more of awireless device information request message and/or an RLF report requestconfigured to request an RLF report for an RLF and/or an HOF.

Based on the request message received from the first base station 1805and/or based on the second RRC message and/or completion of the RAprocedure 1840, the first wireless device 1801 may transmit a reportmessage 1845. The report message 1845 may comprise one or more of awireless device information response message, and/or an RLF report.

The RLF report of the second RRC message and/or of the report messagemay comprise PDCP packet duplication information associated with theprevious RRC connection (e.g., a previous RRC connection associated withthe first base station 1805 or some other base station). The PDCP packetduplication information may comprise, for example: a PDCP packetduplication activation indication, a PDCP packet duplicationconfiguration indication, a bearer identifier of the first bearer, abearer type of the first bearer (e.g., SRB0, SRB1, SRB2, data radiobearer, etc.), a number of bearers that configured for PDCP packetduplication, one or more logical channel identifiers of one or morelogical channels associated with duplicated PDCP packets and/or originalpackets, a duplicated portion of a PDCP packet duplication, a number ofduplications, an RLF cause, one or more cell identifiers of one or morecells employed to transmit original PDCP packets, one or more cellidentifiers of one or more cells employed to transmit duplicated PDCPpackets, one or more base station identifiers of one or more basestations employed to transmit original PDCP packets (e.g., a basestation identifier of the first base station 1805), one or more basestation identifiers of one or more base stations employed to transmitduplicated PDCP packets (e.g., a base station identifier of the firstbase station 1805), etc.

The PDCP packet duplication activation indication may be configured toindicate that one or more bearers (e.g., the first bearer, one or moreSRBs, one or more DRBs, etc.) have been configured for PDCP packetduplication by the first base station 1805 via the first MAC CE messageand/or via the first RRC message (e.g., before the time of theconnection failure). The PDCP packet duplication configurationindication may be configured to indicate that a PDCP packet duplicationfor one or more bearers (e.g., the first bearer, one or more SRBs, oneor more DRBs, etc.) was configured by the first base station 1805 viathe first RRC message (e.g., before the time of the connection failure).The PDCP packet duplication configuration indication may be configuredto indicate that duplicated PDCP packets for one or more bearers (e.g.,the first bearer, one or more SRBs, one or more DRBs, etc.) were beingtransmitted at the time of the connection failure.

The number of bearers configured for PDCP packet duplication mayindicate a number of bearers that were duplicated. The number may be 1,for example, if only the first bearer was duplicated. The number may belarger than 1, for example, if one or more bearers other than the firstbearer were configured and/or activated for PDCP packet duplication.

The duplicated portion of a duplicated PDCP packet may be configured toindicate how much portion of original PDCP packets were duplicated forthe first bearer. The duplicated portion of a duplicated PDCP packet maybe a value between 0% and 100%.

The number of duplications may indicate how many duplications wereconfigured and/or activated for PDCP packets associated with the firstbearer. The number of duplications may indicate how many logicalchannels (e.g., one logical channel for original PDCP packets, and/orone or more logical channels for one or more duplications of originalPDCP packets) for PDCP packets were mapped (e.g., configured and/oractivated) for the first bearer.

The RLF cause may indicate that a reason of the connection failure wasone or more of a number of RLC packet retransmissions (e.g., a number ofRLC packet retransmissions exceeds or meets a threshold value), one ormore out-of-sync detection indications (e.g., an RRC layer receives,from a lower layer, one or more out-of-sync detection indication, and/orthe synchronization was not recovered within a threshold time duration),one or more random access failures (e.g. the first wireless devicefailed in one or more random access attempts), etc.

The first base station 1805 may configure one or more control parametersbased on the one or more elements of the RLF report. The one or morecontrol parameters may comprise one or more handover parameters (e.g., aradio signal received quality threshold, a radio signal received powerthreshold for a handover initiation, etc.), one or more PDCP packetduplication configuration parameters for one or more bearers of one ormore wireless devices, and/or other radio configuration parametersassociated with one or more cells and/or one or more wireless devices.

If PDCP packet duplication for an SRB of a first wireless device 1801was not configured and/or was not activated at the time of theconnection failure, a first base station 1805 may configure and/oractivate an SRB of another wireless device that has similar radio signalmeasurement results to the first wireless device 1801.

The first base station 1805 may initiate a handover of a second wirelessdevice based on the one or more control parameters. The one or morecontrol parameters may be configured based on the one or more elementsof the RLF report. If PDCP packet duplication for an SRB of the firstwireless device 1801 was configured and/or activated at the time of theconnection failure of the first wireless device 1801, the first basestation 1805 may initiate a handover for the second wireless deviceearlier than for the first wireless device 1801 (e.g., if the first basestation 1805 configured and/or activated a PDCP packet duplication foran SRB of the second wireless device).

A first wireless device 1801 may receive, from a first base station1805, a first Radio Resource Control (RRC) message comprising a PacketData Convergence Protocol (PDCP) packet duplication indicationindicating that a plurality of PDCP packets associated with a firstbearer are duplicated. The first wireless device 1801 may receive aMedium Access Control Control Element (MAC CE) message indicating anactivation of transmitting duplicated PDCP packets associated with thePDCP packet duplication indication. The first wireless device 1801 maytransmit one or more duplicated packets associated with the first bearerbased on the PDCP packet duplication indication and/or the MAC CEmessage. The first wireless device 1801 may determine a connectionfailure from a first cell of the first base station 1805. The firstwireless device 1801 may select a second cell of the first base station1805 for an RRC connection to the first base station 1805 based on theconnection failure. The first wireless device 1801 may transmit, to thefirst base station 1805 via the second cell, a second RRC messagecomprising a Radio Link Failure (RLF) report associated with theconnection failure, wherein the RLF report may comprise PDCP packetduplication information indicating one or more of: activation of aduplicated PDCP packet transmission; and/or configuration of PDCP packetduplication for at least one bearer.

The first base station 1805 may configure one or more control parametersbased on the one or more elements of the RLF report. The first basestation 1805 may initiate a handover of a second wireless device basedon the one or more control parameters. The one or more controlparameters may comprise one or more of a radio signal received qualitythreshold or a radio signal received power threshold for a handoverinitiation. The one or more control parameters may comprise one or morePDCP duplication configuration parameters for one or more bearers of oneor more wireless devices.

The connection failure may be one or more of a radio link failure and/ora handover failure. The first base station 1805 may be the first basestation 1805. The first cell may be the second cell. The RLF report maycomprise one or more cell identifiers of one or more cells (e.g., one ormore cells via which the duplicated plurality of PDCP packets of atleast one bearer were transmitted). The first bearer may be a SignalingRadio Bearer (SRB). The determination of the connection failure may bebased on a number of RLC retransmissions of one or more packetsassociated with: original PDCP packets of the first bearer; and/orduplicated PDCP packets of the first bearer. The determination of theconnection failure may be based on: a number of RLC retransmissions; oneor more out-of-sync detections; and/or one or more random accessfailures. The procedures and/or messages of FIG. 18 for a single basestation may comprise some or all of those of, for example, FIG. 16 formultiple base stations.

FIG. 19 shows an example method associated with RLF. The example may beperformed by a wireless device (e.g., the wireless device 1501). One ormore steps of FIG. 19 may be performed by one or more devices (e.g., awireless device and/or a base station). Exemplary devices may bedescribed above in FIGS. 15-18 . At step 1901, the wireless device mayreceive a configuration message. The configuration message may bereceived from a first base station (e.g., the base station 1505). Theconfiguration message may comprise an RRC message comprising bearerconfiguration parameters for a bearer. At step 1905, the wireless devicemay monitor packet transmissions. The packet transmissions may comprisetransmitted or received packets associated with a bearer. At step 1910,the wireless device may determine a connection failure, for example,based on determining one or more criteria. The one or more criteria maycomprise an RLF and/or an HOF. At step 1915, the wireless device mayselect a cell of the first base station or cell of a second base station(e.g., the second base station 1510), for example based on measurementresults of one or more cells. At step 1920, the wireless device mayperform a random access procedure, which may be via a cell. The randomaccess procedure may comprise establishing an RRC connection with a basestation (e.g., the first base station, the second base station, or someother base station). At step 1925, the wireless device may receive arequest for information (e.g., from the first base station, the secondbase station, or some other base station). The request may comprise anindication of a request for an RLF report from the wireless device.

The wireless device may determine whether the RLF report may comprisePDCP packet duplication information. At step 1930, the wireless devicemay determine if the wireless device is or was configured with PDCPpacket duplication capabilities, for example, at a time associated witha connection failure. If the wireless device is or was not configuredwith PDCP packet duplication capabilities, the process may proceed atstep 1950. If the wireless device determines that the wireless device isor was configured with PDCP packet duplication capabilities, thewireless device may add information related to PDCP packet duplicationconfiguration parameters to the RLF report at step 1935. At step 1940,the wireless device may determine if PDCP packet duplication wasactivated for the bearer at the time of the connection failure. If PDCPpacket duplication was activated for the bearer at the time of theconnection failure, the wireless device may add information related tothe activation to the RLF report at step 1945. If the wireless devicedetermines that PDCP packet duplication was not activated for the bearerat the time of the connection failure, the process may proceed at step1950. At step 1950, the wireless device may transmit the RLF report(e.g., to the first base station, the second base station, or some otherbase station).

FIG. 20 shows an example method associated with RLF. The example may beperformed by one or more base stations (e.g., the first base station1505 and/or the second base station 1510). One or more steps of FIG. 20may be performed by one or more devices (e.g., a base station and/or awireless device). Exemplary device may be as described above in FIGS.15-19 . At step 2001, a base station (e.g., the first base station 1505)may transmit a configuration message to a wireless device (e.g., thewireless device 1501). The configuration message may comprise an RRCmessage comprising bearer configuration parameters for a bearer. At step2005, the base station may receive RLF information (e.g., an RLF reportassociated with a wireless device). A first base station may have anactive connection with the wireless device. The first base station mayreceive the RLF report via that connection. The first base station mayreceive a random access preamble from the wireless device. The firstbase station may initiate an RRC connection. The first base station mayrequest information from the wireless device. The first base station mayreceive the RLF report based on the request. A first base station mayalso receive the RLF report indirectly (e.g., via a second basestation). A second base station may obtain an RLF report from thewireless device. The second base station may transmit the RLF report tothe first base station.

The base station (e.g., the first base station 1505) may determinewhether to configure and/or activate PDCP packet duplication. At step2010, the base station may determine if PDCP packet duplication wasconfigured for a bearer at the time of a connection failure (e.g., aconnection failure indicated in the RLF report). If the base stationdetermines that PDCP packet duplication was not configured for a bearerat the time of a connection failure, at step 2015 the base station mayupdate the PDCP packet duplication configuration (e.g., the base stationmay lower a threshold for initiating configuration of PDCP packetduplication). If PDCP packet duplication was configured, at step 2020the base station may determine if PDCP packet duplication was activatedfor a bearer at the time of a connection failure (e.g., a connectionfailure indicated in the RLF report). If the base station determinesthat PDCP packet duplication was not activated for a bearer at the timeof a connection failure, at step 2025 the base station may update one ormore PDCP packet duplication activation parameters. The parameters maybe updated by lowering a threshold for initiating PDCP packetduplication activation. At step 2030, the base station may configureradio resource parameters based on whether PDCP packet duplication wasconfigured and/or activated (e.g., based on an indication of theconfiguration and/or activation). The base station may configure theradio resource parameters by: changing handover parameters (e.g., bylowering a handover threshold associated with neighboring cells),changing parameters to reject inbound handover wireless devices havinglow radio quality, changing parameters to increase signal transmissionpower, and/or changing parameters to increase a number of beamsassociated with the cell. At step 2035, the base station may transmitthe configured radio resource parameters to one or more wireless devices(e.g., the wireless device).

FIG. 21 shows an example method associated with RLF. The example may befrom the perspective of a second base station (e.g., the second basestation 1510). One or more steps of FIG. 20 may be performed by one ormore devices (e.g., a wireless device and/or a base station). Exemplarydevices may be described in FIGS. 15-20 . The second base station mayhave an active connection with a wireless device (e.g., the wirelessdevice 501). The second base station may receive the RLF report via thatconnection. At step 2101, the second base station may receive a randomaccess preamble from the wireless device. The second base station mayinitiate an RRC connection. At step 2105, the second base station mayrequest information from the wireless device. At step 2110, the secondbase station may receive the information. The information may comprisean RLF report. At step 2115, the second base station may transmit theinformation, such as the RLF report from the wireless device, to one ormore other base stations (e.g., a first base station, such as the firstbase station 1505). This may have the advantage of allowing the one ormore other base stations to adjust one or more parameters based oninformation known to the second base station 1510.

The second base station 1510 may adjust one or more handover parametersbased on the RLF report. At step 2120, the second base station 1510 maydetermine if the RLF report indicates that PDCP packet duplication wasconfigured and/or activated for a bearer at the time of a connectionfailure. If PDCP packet duplication was configured and/or activated, atstep 2125 the second base station 1510 may configure inbound and/oroutbound handover parameters for a failed cell. The handover parametersmay be configured by increasing a handover threshold towards the failedcell. The handover parameters may be configured by lowering anacceptance threshold of inbound handover wireless devices from thefailed cell. At step 2130, the second base station 1510 may transmit anindication of the handover parameters to one or more other base stations(e.g., the first base station 1505). This may have the advantage ofallowing the one or more other base stations to adjust parameters basedon the configured handover parameters.

FIG. 22 shows an example architecture for PDCP duplication with dualconnectivity (DC) and carrier aggregation (CA). A PDCP layer 2203 maycomprise an upper level of an MCG 2200, an SCG 2220, or an aggregatedentity 2240. The PDCP layer 2203 may comprise one or more securityelements (e.g., a security element 2206, a security element 2207, asecurity element 2227, a security element 2246, or a security element2243). The security elements may communicate information with one ormore robust header compression (ROHC) elements (e.g., a ROHC 2245 or aROHC 2242). The one or more security elements may connect to one or moresignal bearers (e.g., a signaling radio bearer (SRB) 2202 with packetduplication, or a data radio bearer (DRB) 2241 with packet duplication).The security elements may connect to one or more RLC elements of an RLClayer 2204. The security elements may be connected with multiple RLCelements of an RLC layer 2204, such as by using a duplication element(e.g., a duplication element 2208 or a duplication element 2244).

The RLC layer 2204 may comprise logical processing elements. A logicalprocessing element may comprise one or more segmented automaticrepeat-request (ARQ) elements (e.g., a segmented ARQ 2209, a segmentedARQ 2210, a segmented ARQ 2229, a segmented ARQ 2230, a segmented ARQ2249, a segmented ARQ 2250, or a segmented ARQ 2255). The logicalprocessing elements may be associated with logical channels 2260, andmay be connected with a MAC layer 2205.

The MAC layer 2205 may comprise a lower layer of the MCG 2200, the SCG2220, or the aggregated entity 2240. The MAC layer 2205 may comprisemultiplexers (e.g., a multiplexer 2211, a multiplexer 2231, or amultiplexer 2251). The multiplexers may feed one or more HARQs (e.g., aHARQ 2212, a HARQ 2232, a HARQ 2252, or a HARQ 2256). The HARQs mayprovide transport channels 2270, which may be communicated via one ormore shared channels (e.g., a UL-SCH 2213, a UL-SCH 2233, a UL-SCH onCC1 2253, or a UL-SCH on CC2 2254).

If duplication is configured for a radio bearer (e.g., an SRB 2202 or aDRB 2241) utilizing RRC, an additional RLC entity and/or an additionallogical channel may be added to the radio bearer to handle duplicatedPDCP PDUs. Duplication at the PDCP layer 2203 may consist in aduplication element (e.g., the duplication element 2208 or theduplication element 2244) sending the same PDCP PDUs multiple times(e.g., a first time on the original RLC entity and a second time on theadditional RLC entity). If PDCP PDUs are sent multiple times, theoriginal PDCP PDU and the corresponding duplicate may not be transmittedon the same carrier. Two of the logical channels 2260 may belong to thesame MAC entity 2205 (e.g., for CA) and/or to different ones (e.g., forDC). For CA, logical channel mapping restrictions may be used in MAC toensure that the logical channel carrying the original PDCP PDUs and/orlogical channel carrying the corresponding duplicates may not be sent onthe same carrier.

Duplication may be activated and/or de-activated per DRB (and/or SRB) bymeans of a MAC control element (MAC CE). Activation and/or deactivationof duplication may occur after PDCP packet duplication is configured. InCA, when duplication is de-activated, the logical channel mappingrestrictions may be lifted. In DC, the wireless device may use the MACCE commands regardless of their origin (e.g., the MCG 2200 or the SCG2220).

A PDCP layer of a transmitting node may duplicate PDCP PDUs, andtransmit duplicated packets via a separate logical channel that isdifferent than a logical channel for original packets. A PDCP layer of areceiving node may discard one of duplicate packet and original packet(e.g. discard a packet received later if receiving same packets).

A base station (e.g., a gNB) and/or a wireless device may perform anycombination of a step and/or a complementary step of one or more of thesteps described herein. Any step performed by a gNB may be performed byany base station. A core network device, or any other device, mayperform any combination of a step, or a complementary step, of one ormore of the above steps. Some or all of these steps may be performed,and the order of these steps may be adjusted. Additional steps may alsobe performed. Any base station described herein may be a current basestation, a serving base station, a source base station, a target basestation, or any other base station.

FIG. 23 shows general hardware elements that may be used to implementany of the various computing devices discussed herein, including, e.g.,the base station 401, the wireless device 406, or any other basestation, wireless device, or computing device described herein. Thecomputing device 2300 may include one or more processors 2301, which mayexecute instructions stored in the random access memory (RAM) 2303, theremovable media 2304 (such as a Universal Serial Bus (USB) drive,compact disk (CD) or digital versatile disk (DVD), or floppy diskdrive), or any other desired storage medium. Instructions may also bestored in an attached (or internal) hard drive 2305. The computingdevice 2300 may also include a security processor (not shown), which mayexecute instructions of one or more computer programs to monitor theprocesses executing on the processor 2301 and any process that requestsaccess to any hardware and/or software components of the computingdevice 2300 (e.g., ROM 2302, RAM 2303, the removable media 2304, thehard drive 2305, the device controller 2307, a network interface 2309, aGPS 2311, a Bluetooth interface 2312, a Wi-Fi interface 2313, etc.). Thecomputing device 2300 may include one or more output devices, such asthe display 2306 (e.g., a screen, a display device, a monitor, atelevision, etc.), and may include one or more output device controllers2307, such as a video processor. There may also be one or more userinput devices 2308, such as a remote control, keyboard, mouse, touchscreen, microphone, etc. The computing device 2300 may also include oneor more network interfaces, such as a network interface 2309, which maybe a wired interface, a wireless interface, or a combination of the two.The network interface 2309 may provide an interface for the computingdevice 2300 to communicate with a network 2310 (e.g., a RAN, or anyother network). The network interface 2309 may include a modem (e.g., acable modem), and the external network 2310 may include communicationlinks, an external network, an in-home network, a provider's wireless,coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., aDOCSIS network), or any other desired network. Additionally, thecomputing device 2300 may include a location-detecting device, such as aglobal positioning system (GPS) microprocessor 2311, which may beconfigured to receive and process global positioning signals anddetermine, with possible assistance from an external server and antenna,a geographic position of the computing device 2300.

The example in FIG. 23 is a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 2300 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 2301, ROM storage 2302, display 2306, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 23 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

One or more features of the disclosure may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above mentioned technologiesmay be used in combination to achieve the result of a functional module.

Systems, apparatuses, and methods may perform operations ofmulti-carrier communications described herein. Additionally oralternatively, a non-transitory tangible computer readable media maycomprise instructions executable by one or more processors configured tocause operations of multi-carrier communications described herein. Anarticle of manufacture may comprise a non-transitory tangible computerreadable machine-accessible medium having instructions encoded thereonfor enabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a UE, a base station, and the like) toenable operation of multi-carrier communications described herein. Thedevice, or one or more devices such as in a system, may include one ormore processors, memory, interfaces, and/or the like. Other examples maycomprise communication networks comprising devices such as basestations, wireless devices or user equipment (UE), servers, switches,antennas, and/or the like. A network may comprise any wirelesstechnology, including but not limited to, cellular, wireless, Wi-Fi, 4G,5G, any generation of 3GPP or other cellular standard or recommendation,wireless local area networks, wireless personal area networks, wirelessad hoc networks, wireless metropolitan area networks, wireless wide areanetworks, global area networks, space networks, and any other networkusing wireless communications. Any device (e.g., a wireless device, abase station, or any other device) or combination of devices may be usedto perform any combination of one or more of steps described herein,including, e.g., any complementary step or steps of one or more of theabove steps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner. Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the disclosure. Accordingly, theforegoing description is by way of example only, and is not limiting.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice from a first base station, a packet duplication activationcommand for duplication of one or more data packets; sending, based onthe packet duplication activation command, one or more duplicated datapackets; and sending, by the wireless device to one of the first basestation or a second base station, a radio resource control message thatindicates a connection failure and that indicates that packetduplication was activated at a time associated with the connectionfailure.
 2. The method of claim 1, wherein the radio resource controlmessage comprises a first radio resource control message, and whereinthe method further comprises receiving, from the first base station, asecond radio resource control message comprising one or more packetduplication configuration parameters indicating that at least one of theone or more data packets is duplicated.
 3. The method of claim 1,wherein the one or more duplicated data packets comprise one or moreduplicated packet data convergence protocol (PDCP) packets.
 4. Themethod of claim 1, wherein the connection failure comprises at least oneof: a radio link failure; or a handover failure.
 5. The method of claim1, wherein the connection failure is based on at least one of: aquantity of radio link control retransmissions; an out-of-syncdetection; or a random access failure.
 6. The method of claim 1, whereinthe sending the radio resource control message comprises sending, by thewireless device to the first base station, the radio resource controlmessage.
 7. The method of claim 1, wherein the sending the radioresource control message comprises sending the radio resource controlmessage to the second base station, wherein the second base station isdifferent from the first base station.
 8. The method of claim 1, furthercomprising: determining, by the wireless device, that a quantity ofradio link control (RLC) layer packet retransmissions associated withone or more original packet data convergence protocol (PDCP) packets ofthe one or more data packets satisfies a threshold value; anddetermining, based on a determination that the quantity satisfies thethreshold value, the connection failure.
 9. The method of claim 1,further comprising: determining, by the wireless device, that a quantityof radio link control (RLC) layer packet retransmissions associated withone or more duplicated packet data convergence protocol (PDCP) packetsof the one or more data packets satisfies a threshold value; anddetermining, based on a determination that the quantity satisfies thethreshold value, the connection failure.
 10. The method of claim 1,wherein the radio resource control message is configured to cause thefirst base station to allocate a first quantity of resources for asecond wireless device, wherein the radio resource control messagecomprises a first radio resource control message, wherein the methodfurther comprises sending a second radio resource control message thatindicates a second connection failure and that indicates that packetduplication was deactivated at a time associated with the secondconnection failure, and wherein the second radio resource controlmessage is configured to cause the first base station to allocate asecond quantity of resources for the second wireless device, and whereinthe second quantity is greater than the first quantity.
 11. The methodof claim 1, wherein the connection failure is associated with a firstcell of the first base station, and wherein the sending the radioresource control message comprises sending the radio resource controlmessage via a second cell.
 12. The method of claim 1, furthercomprising: determining the connection failure; and determining, basedon the connection failure, a cell for a radio resource controlcommunication, wherein the sending the radio resource control messagecomprises sending the radio resource control message via the cell. 13.The method of claim 1, wherein the one or more data packets areassociated with a first bearer.
 14. A wireless device comprising: one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the wireless device to: receive, froma first base station, a packet duplication activation command forduplication of one or more data packets; send, based on the packetduplication activation command, one or more duplicated data packets; andsend, to one of the first base station or a second base station, a radioresource control message that indicates a connection failure and thatindicates that packet duplication was activated at a time associatedwith the connection failure.
 15. The wireless device of claim 14,wherein the radio resource control message comprises a first radioresource control message, and wherein the instructions, when executed bythe one or more processors, further cause the wireless device toreceive, from the first base station, a second radio resource controlmessage comprising one or more packet duplication configurationparameters indicating that at least one of the one or more data packetsis duplicated.
 16. The wireless device of claim 14, wherein the one ormore duplicated data packets comprise one or more duplicated packet dataconvergence protocol (PDCP) packets.
 17. The wireless device of claim14, wherein the connection failure comprises at least one of: a radiolink failure; or a handover failure.
 18. The wireless device of claim14, wherein the connection failure is based on at least one of: aquantity of radio link control retransmissions; an out-of-syncdetection; or a random access failure.
 19. The wireless device of claim14, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to send the radio resource controlmessage by sending, to the first base station, the radio resourcecontrol message.
 20. The wireless device of claim 14, wherein theinstructions, when executed by the one or more processors, cause thewireless device to send the radio resource control message by sendingthe radio resource control message to the second base station, whereinthe second base station is different from the first base station. 21.The wireless device of claim 14, wherein the instructions, when executedby the one or more processors, further cause the wireless device to:determine that a quantity of radio link control (RLC) layer packetretransmissions associated with one or more original packet dataconvergence protocol (PDCP) packets of the one or more data packetssatisfies a threshold value; and determine, based on a determinationthat the quantity satisfies the threshold value, the connection failure.22. The wireless device of claim 14, wherein the instructions, whenexecuted by the one or more processors, further cause the wirelessdevice to: determine that a quantity of radio link control (RLC) layerpacket retransmissions associated with one or more duplicated packetdata convergence protocol (PDCP) packets of the one or more data packetssatisfies a threshold value; and determine, based on a determinationthat the quantity satisfies the threshold value, the connection failure.23. The wireless device of claim 14, wherein the radio resource controlmessage is configured to cause the first base station to allocate afirst quantity of resources for a second wireless device, wherein theradio resource control message comprises a first radio resource controlmessage, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to send a second radioresource control message that indicates a second connection failure andthat indicates that packet duplication was deactivated at a timeassociated with the second connection failure, and wherein the secondradio resource control message is configured to cause the first basestation to allocate a second quantity of resources for the secondwireless device, and wherein the second quantity is greater than thefirst quantity.
 24. The wireless device of claim 14, wherein theconnection failure is associated with a first cell of the first basestation, and wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to send the radio resource controlmessage by sending the radio resource control message via a second cell.25. The wireless device of claim 14, wherein the instructions, whenexecuted by the one or more processors, further cause the wirelessdevice to: determine the connection failure; and determine, based on theconnection failure, a cell for a radio resource control communication,and wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to send the radio resource controlmessage by sending the radio resource control message via the cell. 26.The wireless device of claim 14, wherein the one or more data packetsare associated with a first bearer.
 27. A non-transitorycomputer-readable medium storing instructions that, when executed,configure a wireless device to: receive, from a first base station, apacket duplication activation command for duplication of one or moredata packets; send, based on the packet duplication activation command,one or more duplicated data packets; and send, to one of the first basestation or a second base station, a radio resource control message thatindicates a connection failure and that indicates that packetduplication was activated at a time associated with the connectionfailure.
 28. The non-transitory computer-readable medium of claim 27,wherein the radio resource control message comprises a first radioresource control message, and wherein the instructions, when executed,further configure the wireless device to receive, from the first basestation, a second radio resource control message comprising one or morepacket duplication configuration parameters indicating that at least oneof the one or more data packets is duplicated.
 29. The non-transitorycomputer-readable medium of claim 27, wherein the one or more duplicateddata packets comprise one or more duplicated packet data convergenceprotocol (PDCP) packets.
 30. The non-transitory computer-readable mediumof claim 27, wherein the connection failure comprises at least one of: aradio link failure; or a handover failure.
 31. The non-transitorycomputer-readable medium of claim 27, wherein the connection failure isbased on at least one of: a quantity of radio link controlretransmissions; an out-of-sync detection; or a random access failure.32. The non-transitory computer-readable medium of claim 27, wherein theinstructions, when executed, configure the wireless device to send theradio resource control message by sending, to the first base station,the radio resource control message.
 33. The non-transitorycomputer-readable medium of claim 27, wherein the instructions, whenexecuted, configure the wireless device to send the radio resourcecontrol message by sending the radio resource control message to thesecond base station wherein the second base station is different fromthe first base station.
 34. The non-transitory computer-readable mediumof claim 27, wherein the instructions, when executed, further configurethe wireless device to: determine that a quantity of radio link control(RLC) layer packet retransmissions associated with one or more originalpacket data convergence protocol (PDCP) packets of the one or more datapackets satisfies a threshold value; and determine, based on adetermination that the quantity satisfies the threshold value, theconnection failure.
 35. The non-transitory computer-readable medium ofclaim 27, wherein the instructions, when executed, further configure thewireless device to: determine that a quantity of radio link control(RLC) layer packet retransmissions associated with one or moreduplicated packet data convergence protocol (PDCP) packets of the one ormore data packets satisfies a threshold value; and determine, based on adetermination that the quantity satisfies the threshold value, theconnection failure.
 36. The non-transitory computer-readable medium ofclaim 27, wherein the radio resource control message is configured tocause the first base station to allocate a first quantity of resourcesfor a second wireless device, wherein the radio resource control messagecomprises a first radio resource control message, wherein theinstructions, when executed, further configure the wireless device tosend a second radio resource control message that indicates a secondconnection failure and that indicates that packet duplication wasdeactivated at a time associated with the second connection failure, andwherein the second radio resource control message is configured to causethe first base station to allocate a second quantity of resources forthe second wireless device, and wherein the second quantity is greaterthan the first quantity.
 37. The non-transitory computer-readable mediumof claim 27, wherein the connection failure is associated with a firstcell of the first base station, and wherein the instructions, whenexecuted, configure the wireless device to send the radio resourcecontrol message by sending the radio resource control message via asecond cell.
 38. The non-transitory computer-readable medium of claim27, wherein the instructions, when executed, further configure thewireless device to: determine the connection failure; and determine,based on the connection failure, a cell for a radio resource controlcommunication, and wherein the instructions, when executed, configurethe wireless device to send the radio resource control message bysending the radio resource control message via the cell.
 39. Thenon-transitory computer-readable medium of claim 27, wherein the one ormore data packets are associated with a first bearer.
 40. A systemcomprising: a first base station; and a wireless device, wherein thefirst base station is configured to: send, to the wireless device, apacket duplication activation command for duplication of one or moredata packets, and wherein the wireless device is configured to: send,based on the packet duplication activation command, one or moreduplicated data packets; and send, to one of the first base station or asecond base station, a radio resource control message that indicates aconnection failure and that indicates that packet duplication wasactivated at a time associated with the connection failure.
 41. Thesystem of claim 40, wherein the radio resource control message comprisesa first radio resource control message, and wherein the first basestation is further configured to send a second radio resource controlmessage comprising one or more packet duplication configurationparameters indicating that at least one of the one or more data packetsis duplicated.
 42. The system of claim 40, wherein the one or moreduplicated data packets comprise one or more duplicated packet dataconvergence protocol (PDCP) packets.
 43. The system of claim 40, whereinthe connection failure comprises at least one of: a radio link failure;or a handover failure.
 44. The system of claim 40, wherein theconnection failure is based on at least one of: a quantity of radio linkcontrol retransmissions; an out-of-sync detection; or a random accessfailure.
 45. The system of claim 40, wherein, to send the radio resourcecontrol message, the wireless device is configured to send the radioresource control message to the first base station.
 46. The system ofclaim 40, wherein, to send the radio resource control message, thewireless device is configured to send the radio resource control messageto the second base station, wherein the second base station is differentfrom the first base station.
 47. The system of claim 40, wherein thewireless device is further configured to: determine that a quantity ofradio link control (RLC) layer packet retransmissions associated withone or more original packet data convergence protocol (PDCP) packets ofthe one or more data packets satisfies a threshold value; and determine,based on a determination that the quantity satisfies the thresholdvalue, the connection failure.
 48. The system of claim 40, wherein thewireless device is further configured to: determine that a quantity ofradio link control (RLC) layer packet retransmissions associated withone or more duplicated packet data convergence protocol (PDCP) packetsof the one or more data packets satisfies a threshold value; anddetermine, based on a determination that the quantity satisfies thethreshold value, the connection failure.
 49. The system of claim 40,wherein the first base station is further configured to, based on theradio resource control message, allocate a first quantity of resourcesfor a second wireless device, wherein the radio resource control messagecomprises a first radio resource control message, wherein the wirelessdevice is further configured to send a second radio resource controlmessage that indicates a second connection failure and that indicatesthat packet duplication was deactivated at a time associated with thesecond connection failure, wherein the first base station is furtherconfigured to, based on the second radio resource control message,allocate a second quantity of resources for the second wireless device,and wherein the second quantity is greater than the first quantity. 50.The system of claim 40, wherein the connection failure is associatedwith a first cell of the first base station, and wherein, to send theradio resource control message, the wireless device is configured tosend the radio resource control message via a second cell.
 51. Thesystem of claim 40, wherein the wireless device is further configuredto: determine the connection failure; and determine, based on theconnection failure, a cell for a radio resource control communication,and wherein, to send the radio resource control message, the wirelessdevice is configured to send the radio resource control message via thecell.
 52. The system of claim 40, wherein the one or more data packetsare associated with a first bearer.